File locking in Windows may prevent the directory from being deleted.
File locking on Windows is different than file locking on Unix in that on Windows a file can be locked on read. If you are redeploying a second version of an already deployed web application, you may see something like the following web application:
working on a Windows 2000 to 2008 migration, the application uses Tomcat 4.1 running on Windows 2000 server . We are upgrading to Windows 2008 server. Will Tomcat 4.1 work with Windows 2008/IS 7? Has anybody installed Tomcat 4.1 on a Windows 2008 box?
The Apache Tomcat project is developed by a community of volunteers. This is important to remember, since it does have an impact on you as a user. Software being developed, is always developed for use with other software that is current in its era. Apache Tomcat 4, just like Windows 2000, are both 10 years old by now.
So, when the question is asked, will my 10 year old software work on this brand new operating system that didn't even exist when my software was written. The best place for an off shoot question like that is on the mailing lists. Why, well, Apache Tomcat 4.1 is no longer being actively developed. It's been sun setted. So it may or may not work, and if it doesn't, no one will fix it.
In an enterprise environment, one would most likely not plan an upgrade like that. If you have 10 year old software running in your environment, one must ask the questions
If the software will end of life, there would be little meaning spending a great deal of effort upgrading the operating system underneath. If there is a need to upgrade the operating system due to other software needs, then I would isolate my old Java/Apache Tomcat on a virtual machine with the operating system and configuration I know works.
If the software itself will be upgraded, then I would plan a migration path, where I would upgrade
This is not always an easy process, but the bottom line is, the longer you wait, the harder the process becomes. An upgrade like this, will have to start at the web applications, as web applications are not guaranteed to be compatible between different versions of the JSP/Servlet/EL specifications.
Even commerical support vendors will eventually end of life a specific product version. If that time is 3 years, 10 years or 30 years depends on the vendor and the contract itself, but no software lives on forever. When it comes to free and open source software, developed by volunteers, one can expect that timeframe to be in the lower numbers.
If you've recently upgraded the RAM, or are moving your Tomcat applications to a larger box, you may want to update your allocated memory.
To find out how much RAM is allocated already to your Tomcat instance, if you have Tomcat installed as a Windows service, you can run Regedit and look at:
HKEY_LOCAL_MACHINE SOFTWARE Apache Software Foundation Procrun 2,0
Under that key will be all the tomcat service instances you have installed on that machine. If you expand an instance tree you will see another key named Parameters. Expand this and you will see a number of named values:
If you have installed Tomcat without the "Start Menu Items" on Windows it may make it harder to increase max heap size.
An approach to help correct this would be:
How to enable the Java Monitoring and Management Console (JConsole) to monitor performance and resource consumption on Windows.
The JDK 5.0 provides extensive monitoring and management support through the Java Monitoring and Management Console (JConsole) tool. JConsole uses the built-in instrumentation of the Java virtual machine to provide information on performance and resource consumption of applications running on the Java platform using Java Management Extension (JMX) technology.
To enable JConsole for the Tomcat process on Windows:
1. Click on the "java" tab in the Tomcat monitor
2. Add to the java options line.