Article - CS122536
Integrity JVM exited unexpectedly
Modified: 05-Aug-2016
Applies To
- PTC RV&S (formerly Integrity Lifecycle Manager) 2009 to 10.4
Description
- Integrity should prevent simultaneous dumpheap diags to run at the same time.
- Integrity server was automatically restarted
- Prevent simultaneous dumpheap diags to run at the same time in Integrity
- In <Integrity_Server_Installation_Directory>/ there is a file generated with name hs_err_pid<XXXX>.log:
- #
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00000000xxxxxxxx, pid=xxxx, tid=xxxxx
#
# JRE version: 6.0_38-b05
# Java VM: Java HotSpot(TM) 64-Bit Server VM (20.13-b02 mixed mode windows-amd64 compressed oops)
# Problematic frame:
# V [jvm.dll+0x22dc1c]
#
# 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 (0x0000000000cb5000): VMThread [stack: 0x000000001ad10000,0x000000001ae10000] [id=22196]
siginfo: ExceptionCode=0xc0000005, reading address 0x0000000000000110
Registers:
[...]
Register to memory mapping:
RAX=0x0000000000000000 is an unknown value
RBX=
[error occurred during error reporting (printing register info), id 0xc0000005]
Stack: [0x000000001ad10000,0x000000001ae10000], sp=0x000000001ae0f8f0, free space=1022k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
V [jvm.dll+0x22dc1c]
VM_Operation (0x00000000584dcc60): HeapDumper, mode: safepoint, requested by thread 0x000000002c5f0800
- #
This is a printer-friendly version of Article 122536 and may be out of date. For the latest version click CS122536