TomCat service stops unexpectedly

Answers to common questions I have received so far:

• Heapsize: Min = 256MB, Max=512MB.


• Windows is at latest patches.


• I have occasionally seen Windows low-memory warnings, where the virtual memory was automatically increased.


• Server has 12 GB of RAM. Rarely reaches that limit, and never goes anywhere near the max limit with all virtual memory. (27GB)


• Anti-virus is McAfee which is always running. Its' logs do not indicate anything.

Gerry

In Reply to Gerry Champoux:

3 times this week, TomCat (windows service) has stopped for no apparent reason.
It had been working fine for months until now.
The Windows event viewer has entries for the terminated service, but no details.
The TomCat logs do not show anything either.
The last entries prior to the stop do not indicate any problems.
After I restart the service, all is well... until it fails again in a day or 2.

Any suggestions as to what else to look for?

Windchill 9.1 M060 on Windows server 2003 x64.

Yea, we had thissimilar issue when doing a FlexPDM upgrade which is very tomcat intesive and doesn't use method servers much. The oracle temp tablespace would constantly hit the maximum too. The oracle temp tablespace has to adjusted with lots of free space. Check your oracle tables to make sure there is ample free space. Using oracle autoextend is not fast enough or reliable method of performance with Windchill to oracle.Instead of going to clusters of methodservers, I found out it was a version of Java that kept maxing out memory below the maximum heap. Once we updated the Java version, the process was allowed to allocate more memory and thus reduced the demand on CPU to process and build a backlog of threads. Youcan useappdynamics.com to give you better visual reports to narrow down your issue or just watch your memory and CPU on top in Unix. Its hard to watch memory and CPU performance on Windows using task manager. If you see the memoryand CPU maxed out, you should try to add more to the -Xmx like -Xmx2024 or -Xmx3968 in your wttomcat_start. A good idea is to use a minimum of -Xms768Mand just bump up the max memory. We use this in our $TOMCAT_HOME/bin/wttomcat_start:

# Adjust the following heap settings for Windchill
setenv JAVA_OPTS "-server -XX:PermSize=36M -XX:MaxPermSize=128M -Xms768M -Xmx2048M -Djava.awt.headless=true -Dwt.context.defaultLocalResourcesOnly=true"

For the version of Java, have a test server and you should always install $JAVA_HOME as a symbolic link or a folder shortcutas /usr/java/latest or C:\Program Files\Java\latest which points to the specific version you are using (i.e /usr/java/jdk1.6.0_29 or C:\Program Files\Java\jdk1.6.0_29). Then install your windchill applications pointing to that symbolic link/shortcut of java.

that way you can update Java without reseting all the paths in your install. So try a new version of java too. There is always memory fixes in Java.

Good luck.