aspose file tools*
The moose likes Tomcat and the fly likes Old copies of deployed applications linger in temp directory Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Java 8 in Action this week in the Java 8 forum!
JavaRanch » Java Forums » Products » Tomcat
Bookmark "Old copies of deployed applications linger in temp directory" Watch "Old copies of deployed applications linger in temp directory" New topic
Author

Old copies of deployed applications linger in temp directory

Rik Gruwez
Greenhorn

Joined: Mar 30, 2011
Posts: 1
We are using Hudson Continuous Integration to perform nightly builds of our WAR files. These are automatically deployed (hot deployed) to a Tomcat 6 instance. Everything works fine, except that previously deployed applications linger in the the Tomcat/temp directory. Their directory names are prefixed with a number.

For instance on day one we would see in the Tomcat/temp dir the following directory:

1-WarFile

with the 1-WarFile directory containing the complete unzipped WAR file.

The following day it would be
1-WarFile
2-WarFile


1-WarFile still contains all JARs from the WEB-INF lib directory, 2-WarFile contains the newly deployed application.

The next day it would be:
1-WarFile
2-WarFile
3-WarFile


And so on and so forth.

Eventually the disk will fill up and the older directories in the Tomcat/temp directory have to be manually removed.

Any idea why there is not decent cleanup of the Tomcat/temp directory?

Regards,
Rik
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
 
subject: Old copies of deployed applications linger in temp directory
 
Similar Threads
tomcat via java code
content in war file
Can't write Context element properly
String class can't find split method: wrong java version?
What is the best way to share an object across multiple applications