Win a copy of Kotlin in Action this week in the Kotlin forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic

Old copies of deployed applications linger in temp directory  RSS feed

Rik Gruwez
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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:


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

The following day it would be

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:

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?

  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!