Details
-
Feature
-
Status: Released (View Workflow)
-
Minor
-
Resolution: Fixed
-
None
-
None
Description
Current Situation
- When running for Windows the JOC Cockpit deploys its .war file to a temporary directory, e.g. C:\ProgramData\sos-berlin.com\joc\temp
- This directory consumes some 65 MB for each restart of the JOC Cockpit.
- Administrators have to manually clean up the temp directory.
- This behavior does not apply to JOC Cockpit for Linux that cleans up the temp directory.
Desired Behavior
- JOC Cockpit for Windows should clean up its temp directory and behave similar to JOC Cockpit for Linux.
Maintainer Note
- Jetty is already configured to clean up the deployed directories but it doesn't work properly on Windows.
- The cleanup under Windows now takes over an additional servlet when Jetty is started and shutting down
- The "cleanup" procedure of the servlet is called after JOC is completely deployed while Jetty starts so that some time will pass before the old deployed directories are deleted.
- If Jetty is shutting down then the "cleanup" procedure of the servlet will delete all files of the current deployed directory too except the jar files in ./webapp/WEB-INF/lib because access is denied here.