【问题标题】:WebSphere 7.0.0.19 JVM Crash Load Testing RHEL LinuxWebSphere 7.0.0.19 JVM 崩溃负载测试 RHEL Linux
【发布时间】:2013-12-27 04:41:26
【问题描述】:

WebSphere JVM 在执行负载测试时崩溃并生成 .dmp、.txt 和 .trc 文件。

环境详情:

硬件: 架构 x86_64

64 位 CPU 操作模式

CPU 5

内存 16 GB

操作系统: 操作系统 Red Hat Enterprise Linux Server 5.6 (Tikanga)

内核 2.6.18-238.el5

文件限制 8000

最大用户进程数 1024

WebSphere WebSphere 版本 7.0.0.19

初始堆大小 2048 MB

最大堆大小 4096 MB

通用 JVM 参数 -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

最少数据库连接数 1

最大数据库连接数 180

数据库连接超时 180

最小 Web 容器线程大小 50

最小 Web 容器线程大小 75

JVM 详细信息

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

下面是GC的快照

<af type="nursery" id="21" timestamp="Dec 23 19:47:03 2013" intervalms="8681.336">
  <minimum requested_bytes="1160" />
  <time exclusiveaccessms="0.025" meanexclusiveaccessms="0.025" threads="0" lastthreadtid="0x00000000029DF700" />
  <refs soft="37815" weak="31295" phantom="1064" dynamicSoftReferenceThreshold="28" maxSoftReferenceThreshold="32" />
  <nursery freebytes="0" totalbytes="502379520" percent="0" />
  <tenured freebytes="1445056240" totalbytes="1610612736" percent="89" >
    <soa freebytes="1445056240" totalbytes="1610612736" percent="89" />
    <loa freebytes="0" totalbytes="0" percent="0" />
  </tenured>
  <gc type="scavenger" id="21" totalid="39" intervalms="8695.837">
    <flipped objectcount="772517" bytes="49361504" />
    <tenured objectcount="0" bytes="0" />
    <finalization objectsqueued="397" />
    <scavenger tiltratio="82" />
   <nursery freebytes="466161688" totalbytes="516178944" percent="90" tenureage="10" />
   <tenured freebytes="1445056240" totalbytes="1610612736" percent="89" >
     <soa freebytes="1445056240" totalbytes="1610612736" percent="89" />
     <loa freebytes="0" totalbytes="0" percent="0" />
   </tenured>
   <time totalms="37.615" />
 </gc>
 <nursery freebytes="466160528" totalbytes="516178944" percent="90" />
 <tenured freebytes="1445056240" totalbytes="1610612736" percent="89" >
   <soa freebytes="1445056240" totalbytes="1610612736" percent="89" />
   <loa freebytes="0" totalbytes="0" percent="0" />
 </tenured>
 <refs soft="37598" weak="14193" phantom="1064" dynamicSoftReferenceThreshold="28" maxSoftReferenceThreshold="32" />
 <time totalms="57.603" />
  </af>

  <con event="kickoff" timestamp="Dec 23 19:47:03 2013">
    <kickoff reason="Unloading of classes requested" />
    <stats tenurefreebytes="1445056240" nurseryfreebytes="466094992" tracetarget="65473953" kickoff="9082810"  />
  </con>

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 RAX=00007F5FBF6F1300 RBX=0000000000000000
RCX=0000000000001555 RDX=00007F5FBF6F1300 R8=00007F5F1E227E80 R9=0000000000000000
R10=0000000000000384 R11=00000001E1979348 R12=00007F5FCC077980 R13=0000000000000000
R14=00007F5F1E227E80 R15=000000000157DDA0
RIP=00007F5FC5F738E9 GS=0006000000000000 FS=0000000600000000 RSP=00007F5FBC2F67E0
EFlags=0000000000210206 CS=0000000000000033 RBP=00007F5FBF6F1300 ERR=0000000000000006
TRAPNO=000000000000000E OLDMASK=0000000000000000 CR2=0000000000000020
xmm0 0000000000000000 (f: 0.000000, d: 0.000000e+00)
xmm1 0000000040800000 (f: 1082130432.000000, d: 5.346435e-315)
xmm2 0000000000000000 (f: 0.000000, d: 0.000000e+00)
xmm3 00ff000000000000 (f: 0.000000, d: 7.063274e-304)
xmm4 0000000000000000 (f: 0.000000, d: 0.000000e+00)
xmm5 00007f5fb42807a0 (f: 3022522368.000000, d: 6.919341e-310)
xmm6 00007f5fd0b4cca0 (f: 3501509888.000000, d: 6.919365e-310)
xmm7 000000000002010c (f: 131340.000000, d: 6.489058e-319)
xmm8 4350e0198eaee000 (f: 2393825280.000000, d: 1.900000e+16)
xmm9 4024000000000000 (f: 0.000000, d: 1.000000e+01)
xmm10 4297fffffffffd2c (f: 4294966528.000000, d: 6.597070e+12)
xmm11 3e90affee0cce3d1 (f: 3771524096.000000, d: 2.486629e-07)
xmm12 0000000000000000 (f: 0.000000, d: 0.000000e+00)
xmm13 0000000000000000 (f: 0.000000, d: 0.000000e+00)
xmm14 0000000000000000 (f: 0.000000, d: 0.000000e+00)
xmm15 0000000000000000 (f: 0.000000, d: 0.000000e+00)
Module=/home0/was7/IBM/WebSphere/AppServer/java/jre/lib/amd64/compressedrefs/libj9jit24.so
Module_base_address=00007F5FC5BC9000
Target=2_40_20080816_022093_LHdSMr (Linux 2.6.32-71.el6.x86_64)
CPU=amd64 (5 logical CPUs) (0x3ed11e000 RAM)
----------- Stack Backtrace -----------

在网上搜索发现这个链接

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

这表示问题可能是由于页面缓存,但 WAS 版本与上面链接中提到的不同。在这方面需要一些帮助。

谢谢。

【问题讨论】:

  • 这听起来像是 JVM 缺陷。我建议更新到最新的修订包级别。如果问题仍然存在,我建议向 IBM 开一个 PMR。
  • 感谢@bkail 更新 JVM 后问题已解决。

标签: java websphere-7 jvm-crash rhel5


【解决方案1】:

我在 JVM 中禁用了压缩引用,并解决了问题

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

【讨论】:

  • 我建议您尝试使用修订包或限制磁盘缓存。禁用压缩引用会对性能产生相当大的影响。
猜你喜欢
  • 2018-05-28
  • 2011-01-15
  • 2018-01-11
  • 2010-10-06
  • 1970-01-01
  • 1970-01-01
  • 1970-01-01
  • 1970-01-01
  • 1970-01-01
相关资源
最近更新 更多