JVM is Crashing Upon Upgrading to Apache Tomcat 4.1

posted by SpringSource on March 15, 2010 06:32 PM

Using -Xincgc and -verbose:gc in starting JVM to help isolate problems.

In general, garbage collection is more extensive in Tomcat 4.1 than that of 4.0. However, the cause for JVM crashing might lie somewhere else. Using -Xincgc and -verbose:gc in starting JVM would help in isolating where the problem might come from. You can follow the steps below to complete this process:

1. Stop Tomcat
2. Delete jvm.stdout in c:/covalent/ers/servers//logs folder
3. Take out the -Xincgc switch in the wrappers.properties file
4. Start Tomcat
5. Access the application until the slow performance is seen
6. Stop Tomcat
7. Rename jvm.stdout
8. Add -Xincgc switch back in the wrappers.properties file
9. Start Tomcat
10. Repeat the sequence of steps in Step 5
11. Stop Tomcat
12. Compare jvm.stdout and the previously renamed jvm.stdout

Analyzing the garbage collection logs should provide you with some insight into the root cause if it is an application specific issue or NIC configuration issue.

For more than 10 years, SpringSource employees have been supporting Apache technologies, with unparalleled experience and commitment to the Apache Software Foundation. More than 400 of the Fortune 500 count on SpringSource to support their mission-critical business applications. Leaders of the Apache Software Foundation, including Board Members, work at SpringSource and dedicate a significant amount of time further developing the Apache Tomcat open source project. Over the last 2 years, 95% of the issues fixed in the Apache Tomcat project were fixed by SpringSource engineers. For more information on how SpringSource can help your enterprise, see the SpringSource website, or call 800/444-1935.