Seeing following errors in the logs
18:47:52.786 0x33c72600 j9mm.107 * ** ASSERTION FAILED ** at MarkingScheme.cpp:325: ((objectPtr != ((j9object_t)((UDATA)-1))))
JVMDUMP006I Processing dump event "traceassert", detail "" - please wait.
JVMDUMP032I JVM requested System dump using 'SOMEPATH/core.20121015.114752.23855198.0001.dmp' in response to an event
jextract, dumpview and other IBM Support Assistant tools are also not able to process that dmp. The tools are giving errors that no JVM found in dump. If jdk tools itself not able to read system dumps, is it jvm bug?
Here is the java version
java version "1.6.0"
Java(TM) SE Runtime Environment (build pap3260sr5-20090529_04(SR5))
IBM J9 VM (build 2.4, J2RE 1.6.0 IBM J9 2.4 AIX ppc-32 jvmap3260sr5-20090519_35743 (JIT enabled, AOT enabled)
J9VM - 20090519_035743_bHdSMr
JIT - r9_20090518_2017
GC - 20090417_AA)
JCL - 20090529_01
NOTICE: developerWorks Community will be offline May 29-30, 2015 while we upgrade to the latest version of IBM Connections. For more information, read our upgrade FAQ.
This topic has been locked.
3 replies Latest Post - 2013-06-05T10:22:58Z by S2ST_zhao_yi
Pinned topic JVM Crashed with "Assertion Failed" Error
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2012-12-19T00:15:30Z at 2012-12-19T00:15:30Z by SystemAdmin
Re: JVM Crashed with "Assertion Failed" Error2012-11-05T10:04:37Z in response to SystemAdminYour environment uses bit old service level. The current 1.6 service level SR11.
Recommended to use the latest level. If problem is reproduced with the latest level, share the logs.