When just deleting an empty directory the ordering of the deletion doesn't matter. If we start deleting the entire directory hierarchy including files that Tomcat has written, the ordering becomes important. That means that we can't use a shutdown hook as the hook that closes the context and stops Tomcat and the hook that deletes the directory hierarchy may run in any order or in parallel.
To implement this, I think we'd need to add something to the WebServer implementation that triggers the deletion of the temporary directory hierarchy as part of its stop processing. Thanks, we are facing the same issue where many of these empty folders are created for each test run and not deleted. I was facing the same issue with the login Spring security , on Windows tho , i've been on it for hours.
To get the PID, check your console. Skip to content. Star New issue. Jump to bottom. Labels type: enhancement. Milestone 2. Copy link. Using Spring Boot 1. I think that deleteOnExit method doesn't work if the directory is not empty That's correct. A JVM shutdown hook could resolve this issue import org.
A JVM shutdown hook could resolve this issue Thanks for the suggestion, but if we always cleared out the whole directory on exit, we'd then get complaints from users who wanted it to remain. Thanks, that solves my issue :. I have been using Tomcat for quite a while now but I am not sure what the " temp " and " work " directories are used for and when I need to clean which. Can anyone please advise?
Improve this question. Add a comment. Active Oldest Votes. Improve this answer. StackzOfZtuff 1, 21 21 silver badges 20 20 bronze badges. Robert Robert 2, 19 19 silver badges 12 12 bronze badges.
Robert: thanks! Can you tell me under which directory the session data is stored? Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Connect and share knowledge within a single location that is structured and easy to search. I have a library that creates a few temp files in java.
Hope not! Second question, I want to make sure my tempfiles are automatically cleaned up when the JVM quits or is aborted. They are very ephemeral files, and in proper use, there will never be any clutter, but there could be crashes and other causes for my temp files not being deleted. Then I register a shutdown hook, and knowing the path of the folder used by my vm instance, I iterate this folder on shutdown and delete all the files in it, and then delete the folder.
This would seem to work on linux, based on the fact that you can delete open files, but there is no guarantee with my library that the clients of the temp file streams will have closed all their streams before the shutdown hook is called, so on windows the files would not be deleted.
That's a problem. Also, some containers may not allow shutdown hooks, and even if they do, there is no absolute guarantee that the shutdown hook is called. What I wish for is some reliable way to clean up garbage my library created on startup such that this approach will work for several JVMs running on the same machine.
This depends on whether there are cleanup scripts running. Once it's closed the filesystem will release the space automatically. If the JVM crashes or exits normally, the space is automatically released and there are no trash temp-files on the filesystem. With Windows, it is a bit more problematic, and you may need to implement periodic sweeps that attempts File. Yes, creating a temp folder for temp files is good choice and i see no harm in doing it.
You can build a auto-delete routine in your library to delete temp files which are older than x amount of days or hours and you can make this time configurable for user to specify this time and create a default value.
0コメント