Tomcat/Java compiler crash

[Mark Fisher_4]

We have a vendor application being deployed with Tomcat. The versions of Tomcat and java are:

Tomcat is 5.0.28 (required by vendor)
java is 1.4.2.10 (required by vendor)

Tomcat is randomly crashing with the following:

SIGSEGV 11* segmentation violation
si_signo [11]: SIGSEGV 11* segmentation violation
si_errno [0]: Error 0
si_code [2]: SEGV_ACCERR [addr: 0xc00]


Aborting...

Unexpected Signal : 11 occurred at PC=0xC56EF780
Function=_ZN7RegMask3ANDERKS_
Compiler thread crashed while compiling a method!
Compiled method class=ibi.broker.util.RCDES
Compiled method name=getStringFromHexString
Compiled method signature=(Ljava/lang/String;)Ljava/lang/String;
Library=/opt/java1.4/jre/lib/IA64N/server/libjvm.so

Current Java thread:
"CompilerThread0" daemon prio=7 tid=00064c50 nid=9 lwp_id=3017 runnable [0x00000
000..0x6a4001f8]


This is a problem with java compiling a method out of a class/jar file, correct? So, I added the following directive in the catalina.sh file for the JAVA_OPTS:

-XX:CompileCommand= exclude,ibi/broker/util/RCDES,getStringFromHexString

This should prevent the suspect method from getting compiled. And it does. The catalina.out file has

### Excluding compile: ibi.broker.util.RCDES::getStringFromHexString

which verifies this.

Well, then vendor thinks this is a problem with either Tomcat or Java. In fact, they recommended we log a call with HP. And of course, these products are not owned by HP.

So, does anyone think this is really a Tomcat or Java problem or a problem with the vendors method? I was able to find the jar file with the class file that contains this method. Since this is in a class file, is there a way to manually compile this method to see if I can reproduce the problem?

[Steven E. Protter · Accepted solution]

Shalom,

It is quite possible vendor requirements are crashing your system.

Prior to that, put in the latest OS patch set and everything you can get your hands on that relates to java.

swverify \*
# makes sure everything that is installed is not corrupt.

You do not mention your source for Tomcat and the other applications. If possible, HP should be your source here.

SEP

[Arunvijai_4]

Hi,

I would recommend to update patches as SEP specified, here are the details http://h18012.www1.hp.com/java/patches/index.html

Also, Are you able to reproduce this problem with Latest version of Java 5.0 ? If yes, you can log a call with HP customer support.

http://www.hp.com/products1/unix/java/java2/jdkjre5_0/index.html

-Arun

[Mark Fisher_4]

Thanks guys, good point about patches. I ran a HP/UX patch assesment and need a lot of patches. Hope to get these in soon. I should be able to install java 1.5 and setup Tomcat to run with it and see how it works.

Thanks again...

[Mark Fisher_4]

Well, amazingly enough, Java 1.5 fixed the problem even though the vendor said their styff runs under 1.4.