It's all about the answers!

Ask a question

CLM 4.0.0 + WAS + RHEL 6 - Startup Fails

Justin Spies (2812) | asked Sep 14 '12, 4:47 p.m.
I've recently installed CLM 4.0.0 on an RHEL6 system and when I try to start WAS, the startup fails with:
JVMDUMP006I Processing dump event "gpf", detail "" - please wait.
JVMDUMP007I JVM Requesting System dump using '/opt/IBM/WebSphere/AppServer/profiles/AppSrv01/core.20120914.150239.1790.0001.dmp'
Unhandled exception
Type=Segmentation error vmState=0x00000000
J9Generic_Signal_Number=00000004 Signal_Number=0000000b Error_Value=00000000 Signal_Code=00000001
Handler1=00007F4F4DD47780 Handler2=00007F4F4DA0AF20 InaccessibleAddress=00000000E941A8E8
RDI=00000000023868B0 RSI=00007F4F348CCEEA RAX=0000000000000007 RBX=0000000002385CC0
RCX=00007F4F34146448 RDX=00000001E9405588 R8=00000000E941A8E8 R9=0000000000000000
R10=0000000000000000 R11=0000000000000002 R12=0000000000638BD0 R13=00007F4F4E0CDEA0
R14=00007F4F4DEA7CA0 R15=00007F4F38384CA0
RIP=00007F4F4DD50D31 GS=0004000000000000 FS=0000000400000000 RSP=00007F4F34146430
EFlags=0000000000210206 CS=0000000000000033 RBP=000000000228AA00 ERR=0000000000000004
TRAPNO=000000000000000E OLDMASK=0000000000000000 CR2=00000000E941A8E8

In section 4 of the documentation, I've completed the steps for configuring WAS, configuring LDAP, and deploying the CLM WAR files. I can deploy the WAR files, but when I try to start the applications, the WAS instance crashes. Restarts of the WAS instance meet with the above error in the profiles/AppSrv01/logs/server1/native_stderr.log file.

One thing I did different -- for the JVM options, I originally added the '-Xgc:preferredHeapBase=0x100000000' command line argument in the WAS console. When I shutdown and restarted WAS to enact the JVM configuration options, however, Java complained that 'preferredHeapBase' is an unknown option and WAS wouldn't start. Here is an example:

[root@clmappst02 server1]# /opt/IBM/WebSphere/AppServer/java/jre/bin/java -Xquickstart -Xmn512m -Xgcpolicy:gencon -Xcompressedrefs -Xgc:preferredHeapBase=0x100000000 -Xmx4096
JVMJ9GC040E Unknown option: preferredHeapBase=0x100000000
JVMJ9VM015W Initialization error for library j9gc24(2): Failed to initialize; unable to parse command line
Could not create the Java virtual machine.

Here is my JVM version info:

[root@clmappst02 server1]# /opt/IBM/WebSphere/AppServer/java/jre/bin/java -version
java version "1.6.0"
Java(TM) SE Runtime Environment (build pxa6460sr2-20080818_01(SR2))
IBM J9 VM (build 2.4, J2RE 1.6.0 IBM J9 2.4 Linux amd64-64 jvmxa6460-20080816_22093 (JIT enabled, AOT enabled)
J9VM - 20080816_022093_LHdSMr
JIT  - r9_20080721_1330ifx2
GC   - 20080724_AA)
JCL  - 20080808_02

Has anyone else run into this, or similar, issues? I've double checked all the RPM pre-requisites for installing WAS. It even runs great without the CLM apps deployed. As soon as they are deployed, however, BOOM, no workie.

Accepted answer

permanent link
Rosa Naranjo (2.9k11422) | answered Sep 15 '12, 11:52 a.m.
How much memory does your machine have? If you are using the recommendations to start with a 4 gb heap, then you need to have at least 6 or better 8 gb ram on your server. I also do not see the -Xms 4g parameter in your post.  The -Xgc:preferredHeapBase option should have worked.  Make sure you are adding the jvm params to the correct area in the console.  Also, make sure that when you applied the fixpack 23 to WAS that you also applied the corresponding fixpack for the jvm.

Here is the work item that was used to track and settle on the recommended jvm settings for 4.0.
Task 198140
Justin Spies selected this answer as the correct answer

Justin Spies commented Sep 18 '12, 11:40 a.m.

Found out that the FP for the JVM was missing :/ Thanks for the suggestion!

Your answer

Register or to post your answer.