Topic
No replies
Anant007
Anant007
1 Post
ACCEPTED ANSWER

Pinned topic WebSphere 7.0.0.19 JVM Crash Load Testing RHEL Linux

‏2013-12-27T05:44:06Z |

WebSphere JVM crashes while performing load testing and generates .dmp, .txt and .trc files.

Environment details:

HW: Architecture x86_64

CPU op-mode(s) 64-bit

CPU(s) 5

RAM 16 GB

OS: Operating System Red Hat Enterprise Linux Server release 5.6 (Tikanga)

Kernel 2.6.18-238.el5

File Limit 8000

Max User Processes 1024

WebSphere WebSphere Version 7.0.0.19

Initial Heap Size 2048 MB

Maximum Heap Size 4096 MB

Generic JVM arguments -XX:+HeapDumpOnOutOfMemoryError -XX:MaxPermSize=1024m -XX:+CMSClassUnloadingEnabled -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+PrintHeapAtGC -Djavax.management.builder.initial= -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.port=1099

Minimum DB Connections 1

Maximum DB Connection 180

DB Connection Time Out 180

Minimum Web Container Thread Size 50

Minimum Web Container Thread Size 75

JVM Details

NULL ------------------------------------------------------------------------



0SECTION 
     ENVINFO subcomponent dump routine
NULL           
=================================
1CIJAVAVERSION 
J2RE 
6.0 
IBM J9 
2.4 
Linux 
amd64
-
64 
build jvmxa6460
-
20080816
_22093
1CIVMVERSION 
VM build 
20080816
_022093_LHdSMr
1CIJITVERSION 
JIT enabled
, 
AOT enabled 
- 
r9_20080721_1330ifx2
1CIGCVERSION 
GC  
20080724
_AA_CMPRSS
1CIRUNNINGAS 
Running 
as a standalone JVM

Below is the snapshot of the GC

Unhandled exception



Type
=
Segmentation 
error vmState
=
0x00000000
J9Generic_Signal_Number
=
00000004 
Signal_Number
=
0000000b 
Error_Value
=
00000000 
Signal_Code
=
00000001
Handler1
=
00007F5FD09EC780 
Handler2
=
00007F5FD06AFF20 
InaccessibleAddress
=
0000000000000020 
RDI
=
00007F5FCC077980 
RSI
=
000000000157DDA0 

 

On searching the internet found this link

http://www-01.ibm.com/support/docview.wss?uid=swg21499624

which says the issue could be because of page cache, but WAS version is different as mentioned in the link above. Require some help on this.

Attached is Java Core Dump & native_stderr.log

Thanks.

 

Updated on 2013-12-27T05:47:00Z at 2013-12-27T05:47:00Z by Anant007