Do you spend too much time sifting through Google results to find answers to your Apache Tomcat Questions? Now is your chance to learn undocumented secrets of Apache Tomcat. If you are using or considering using Apache Tomcat and would like to improve your knowledge, join Apache experts and committers Mark Thomas and Filip Hanik as they outline the top Tips and Tricks to make management and administration of Apache Tomcat easier, faster and more productive.
EMBEDDED PRESENTATION SLIDES (i.e. user can click “Next” thru slides)
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:
In the past, deploying Apache Tomcat in medium and large enterprise environments presented significant challenges due to the rudimentary management tools in Apache Tomcat. But no longer. SpringSource provides an enterprise version of Apache Tomcat, complete with all the enterprise features necessary for managing large scale Apache Tomcat deployments.
In this webinar, Apache Tomcat committers Mark Thomas and Filip Hanik discuss performance tuning Apache Tomcat for your production environment. This webinar focuses on Tuning Tomcat and the JVM to correctly handle your application including usage patterns, hardware and network topology. You’ll learn when and how to apply the different tuning and configuration options as well as understanding load balancers and how they can impact your configuration settings. Also discussed: the impact of clustering and replication on your environment.
There is absolutely no risk moving to such a platform. 64bit JVMs are also common, but are only used when the applications require lots of memory space, to go over the 32bit memory barrier
Moving Tomcat to either
is not an issue. It has been proven in numerous enterprise environments.
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:
When jvisualvm profiler is connected to tcServer 6.0.19A, JVM crashes. The new XML parser in Tomcat 6.0.19 and Tomcat 6.0.20 is case-sensitive and may be related to this problem. Turn off the default settings of compiling classes with debug information, it should prevent JVM for tcServer from crashing.