IdP 3.3.1.1 on windows creates new copy of lib jars in jetty-base/tmp every restart

[Cantor, Scott]

On 8/24/17, 3:53 PM, "Cantor, Scott" <cantor.2 at osu.edu> wrote:

> All I've ever set in my non-Windows environment is -Djava.io.tmpdir=tmp in start.ini and I've never noticed it does anything
> horrible but I'll take a look and see if it's not cleaning itself up.

It generally is cleaning itself. There are a handful of older copies not cleaned up but clearly not every time (I see as few as 2 old copies on a production server). And the mechanism you found is simply the same thing as globally setting the tmp location, just on a per-app basis. So it has no impact on whether it cleans itself or not. I think you're experiencing an issue causing it to not clean up, and that's environmental. I don't have any specific explanation in my case for why I see a few old ones, but I'm sure it's just a matter of how the shutdown happens.

If changing the location matters, that would suggest permissions might be involved.

-- Scott