• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Liutauras Vilda
  • Jeanne Boyarsky
  • Devaka Cooray
  • Paul Clapham
Sheriffs:
  • Tim Cooke
  • Knute Snortum
  • Bear Bibeault
Saloon Keepers:
  • Ron McLeod
  • Tim Moores
  • Stephan van Hulst
  • Piet Souris
  • Ganesh Patekar
Bartenders:
  • Frits Walraven
  • Carey Brown
  • Tim Holloway

Old copies of deployed applications linger in temp directory

 
Greenhorn
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:

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.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!