jvm crash due to SIGSEG on linux (cent OS) - Jboss5.1 is going down once in a wek

[jbosstaskmgmt2]

#

# A fatal error has been detected by the Java Runtime Environment:

#

#  SIGSEGV (0xb) at pc=0x00002ad83d8bf744, pid=14784, tid=46913610172736

#

# JRE version: 6.0_20-b02

# Java VM: Java HotSpot(TM) 64-Bit Server VM (16.3-b01 mixed mode linux-amd64 )

# Problematic frame:

# V  [libjvm.so+0x33e744]

#

# If you would like to submit a bug report, please visit:

#   http://java.sun.com/webapps/bugreport/crash.jsp

#

---------------  T H R E A D  ---------------

Current thread (0x00002aaaea58a800):  JavaThread "ajp-jbackxxxl.x.xxx.com%2Fxx.xxx.xx.xx-8009-23" daemon [_thread_in_vm, id=15067, stack(0x00002aaaed01c000,0x00002aaaed11d000)]

siginfo:si_signo=SIGSEGV: si_errno=0, si_code=1 (SEGV_MAPERR), si_addr=0x0000000000000000

Registers:

RAX=0x0000000000000001, RBX=0x00002aaaed11b1e0, RCX=0x00002aaaaec273af, RDX=0x0000000000000000

RSP=0x00002aaaed11af80, RBP=0x00002aaaed11af90, RSI=0x00002aaaed11b210, RDI=0x00002aaaae948de0

R8 =0x0000000000000000, R9 =0x0000000000000000, R10=0x00002aaaae97ade0, R11=0x00002aaaed11b1e0

R12=0x00002aaaea58a800, R13=0x00002aaaea58a9b8, R14=0x0000000000000000, R15=0x00002aaaed11b248

RIP=0x00002ad83d8bf744, EFL=0x0000000000010246, CSGSFS=0x0000000000000033, ERR=0x0000000000000004

  TRAPNO=0x000000000000000e

Top of Stack: (sp=0x00002aaaed11af80)

0x00002aaaed11af80:   00002aaaea58a800 00002aaaed11b210

0x00002aaaed11af90:   00002aaaed11b580 00002ad83d9c6c23

0x00002aaaed11afa0:   00002aaaed11b1e0 00002aaaed11afc0

0x00002aaaed11afb0:   00002aaacd294c70 00002aaacd294c68

0x00002aaaed11afc0:   000000004eaae090 000000004eaae068

0x00002aaaed11afd0:   00000000870cb7f0 00002aaaed11afd8

0x00002aaaed11afe0:   000000020cdd5df1 00002aaaed11b050

0x00002aaaed11aff0:   000000020cdd6aa8 0000000000000000

0x00002aaaed11b000:   000000020cdd5e68 0000000000000000

0x00002aaaed11b010:   00002aaaed11b040 00002aaaed11b098

0x00002aaaed11b020:   00002aaaae949b02 000000009beadcd0

0x00002aaaed11b030:   000000020762ee60 0000003bd3c8c2dd

0x00002aaaed11b040:   000000004eaae090 00002ad83db57023

0x00002aaaed11b050:   000000004e7739b0 000000000006fdca

0x00002aaaed11b060:   000000008706b1c8 00002aaaaea0c100

0x00002aaaed11b070:   00002aaaed11b0c0 0000000207612128

0x00002aaaed11b080:   000000004ad76d88 00002aaaae96ea09

0x00002aaaed11b090:   00002aaaaea2aff8 000000004eab26b0

0x00002aaaed11b0a0:   000000004e7739b0 000000004eab26a0

0x00002aaaed11b0b0:   000000004e7739b0 000000005f0e0644

0x00002aaaed11b0c0:   000000008706b1c8 0000000207822b98

0x00002aaaed11b0d0:   00002aaaed11b140 00002aaaae949e83

0x00002aaaed11b0e0:   0000000207654470 00002aaaae949e83

0x00002aaaed11b0f0:   000000004ad70188 000000004e85bce8

0x00002aaaed11b100:   00002aaaed11b028 00002aaaed11b068

0x00002aaaed11b110:   00002aaaed11b0f1 0000000800000001

0x00002aaaed11b120:   000000020fa8ed00 000000020cdb1450

0x00002aaaed11b130:   00002aaa0000000c 0000000000000000

0x00002aaaed11b140:   00002aaaaec27210 00002aaa00000000

0x00002aaaed11b150:   0000000000000000 00002aaaed11b4f0

0x00002aaaed11b160:   00002aaaed110140 00002aaaae9499a9

0x00002aaaed11b170:   00002aaaed11b098 00002aaaed11b0d8

Instructions: (pc=0x00002ad83d8bf744)

0x00002ad83d8bf734:   48 8b 5d f8 c9 c3 66 66 90 66 66 90 48 8b 56 20

0x00002ad83d8bf744:   48 8b 32 48 8b 7a 08 48 8d 4a 10 48 89 0b 48 89

Stack: [0x00002aaaed01c000,0x00002aaaed11d000],  sp=0x00002aaaed11af80,  free space=3fb0000000000000018k

Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)

V  [libjvm.so+0x33e744]

V  [libjvm.so+0x445c23]

C  [libjava.so+0x10e3e]  Java_java_security_AccessController_doPrivileged__Ljava_security_PrivilegedAction_2+0xe

C  0x00002aaab08baee8

C  0x00002aaaae949b02

C  0x00002aaaae949fdc

C  0x00002aaaae949fdc

C  0x00002aaaae949fdc

C  0x00002aaaae949fdc

C  0x00002aaaae949fdc

Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)

C  0x00002aaaaec273af

[error occurred during error reporting (printing Java stack), id 0xb]

Could some one please help me to figure out the problem.

[peterj]

JDK 6.0_20 is pretty old. Try running with a more recent JDK. If the problem still persists with the never JDK, you will have to file a bug report with Oracle.

[jbosstaskmgmt2]

Thanks for the suggestion.  It has been working fine in production for last 1 yr, but all of sudden it started behaving like this.  I am planning to upgrade it to JDK1.7.0.  If it doesn't fix the problem, I would certainly report it to Oracle.