APAR status
Closed as program error.
Error description
Error Message: A segmentation fault occurs in j9bcv_verifyBytecodes after the system has exhausted native memory. . Stack Trace: XMTHREADINFO3 Java callstack: 4XESTACKTRACE at java/lang/J9VMInternals.verifyImpl(Native Method) 4XESTACKTRACE at java/lang/J9VMInternals.verify(J9VMInternals.java:93(Compiled Code)) 4XESTACKTRACE at java/lang/J9VMInternals.verify(J9VMInternals.java:91(Compiled Code)) 4XESTACKTRACE at java/lang/J9VMInternals.verify(J9VMInternals.java:91(Compiled Code)) 4XESTACKTRACE at java/lang/J9VMInternals.initialize(J9VMInternals.java:170(Compil ed Code)) 4XESTACKTRACE at java/lang/J9VMInternals.newInstanceImpl(Native Method) 4XESTACKTRACE at java/lang/Class.newInstance(Class.java:1557(Compiled Code)) 4XESTACKTRACE at com/ibm/xtq/xslt/jaxp/TemplatesImpl.getTransletInstance(Bytecode PC:41(Compiled Code)) 4XESTACKTRACE at com/ibm/xtq/xslt/jaxp/TemplatesImpl.newTransformer(Bytecode PC:5(Compiled Code)) 5XESTACKTRACE (entered lock: com/ibm/xtq/xslt/jaxp/TemplatesImpl@0x3F86FC40, entry count: 1) 4XESTACKTRACE at com/ibm/xtq/xslt/jaxp/AbstractTransformerFactory.newTransformer( Bytecode PC:11(Compiled Code)) 4XESTACKTRACE at testcases/xml/xalan/Examples.exampleUseAssociated(Examples.java: 992) 4XESTACKTRACE at testcases/xml/xalan/Examples.run(Examples.java:305(Compiled Code)) 4XESTACKTRACE at com/ibm/jtc/test/jltf/workunitadapters/JGrinderWorkUnit.runWork( JGrinderWorkUnit.java:441) 4XESTACKTRACE at com/ibm/jtc/test/jltf/threads/WorkUnitRunner.run(WorkUnitRunner. java:113) 4XESTACKTRACE at com/ibm/jtc/test/jltf/threads/pooling/PooledRunnable.runWork(Poo ledRunnable.java:170) 4XESTACKTRACE at com/ibm/jtc/test/jltf/threads/pooling/PooledRunnable.getAndRunWo rk(PooledRunnable.java:136(Compiled Code)) 4XESTACKTRACE at com/ibm/jtc/test/jltf/threads/pooling/PooledRunnable.run(PooledR unnable.java:93) 4XESTACKTRACE at com/ibm/jtc/test/jltf/threads/PooledLangThreadFactory$JavaLangPo oledThread.run(PooledLangThreadFactory.java:152) 3XMTHREADINFO3 Native callstack: 4XENATIVESTACK protectedIntrospectBacktraceSymbols+0x17e (, 0x22D945FE) 4XENATIVESTACK j9sig_protect+0x67a ( 0x22DAF60A) 4XENATIVESTACK j9introspect_backtrace_symbols+0x17e (, 0x22D94536) 4XENATIVESTACK JavaCoreDumpWriter::writeThreadSection()+0x724 (, 0x22E92574) 4XENATIVESTACK protectedWriteSection+0x14 ( 0x22E8E424) 4XENATIVESTACK j9sig_protect+0x67a ( 0x22DAF60A) 4XENATIVESTACK ( 0x22E8D510) 4XENATIVESTACK runJavadump+0x18 (, 0x22E9A680) 4XENATIVESTACK doJavaDump+0x4fa (0x22E71932) 4XENATIVESTACK protectedDumpFunction+0x1e (, 0x22E71B9E) 4XENATIVESTACK j9sig_protect+0x67a ( 0x22DAF60A) 4XENATIVESTACK runDumpAgent+0x362 (, 0x22E74952) 4XENATIVESTACK triggerDumpAgents+0x496 (0x22EA7FCE) 4XENATIVESTACK generateDiagnosticFiles+0x1d0 (, 0x22C4A138) 4XENATIVESTACK j9sig_protect+0x67a ( 0x22DAF60A) 4XENATIVESTACK structuredSignalHandler+0x1b0 ( 0x22C4B9D0) 4XENATIVESTACK masterSynchSignalHandler+0x20a ( 0x22DAD75A) 4XENATIVESTACK (, 0x214349E4) 4XENATIVESTACK __zerros+0x1d8 (, 0x21433EC8) 4XENATIVESTACK CEEVROND+0x1200 (, 0x0C5F96E8) 4XENATIVESTACK (, 0x0C4EC6D8 <OSB>CEEHDSP+0xd60<CSB>) 4XENATIVESTACK (, 0x0C4FAE6E <OSB>CEEHRNUH+0x96<CSB>) 4XENATIVESTACK j9bcv_verifyBytecodes+0xb4e (, 0x2420C3B6) 4XENATIVESTACK SENDINITIALIZE+0x1ccf1d8 (, 0x248F0620) 4XENATIVESTACK RUNJAVATHREAD+0x1cd1a1e (, 0x248EFF06) 4XENATIVESTACK javaProtectedThreadProc+0xd2 (, 0x22CAF3A2) 4XENATIVESTACK j9sig_protect+0x67a ( 0x22DAF60A) 4XENATIVESTACK javaThreadProc+0x54 ( 0x22CB1714) 4XENATIVESTACK thread_wrapper+0x3ec (, 0x22D2087C) 4XENATIVESTACK CEEVROND+0x1200 (, 0x0C5F96E8) 4XENATIVESTACK (, 0x00B9EF12 <OSB>CEEOPCMM+0x96a<CSB>) . The following tracepoint will have recently fired if this is the same issue: 15:54:37.686878750 *0x4882a300 j9vm.302 Entry >setCurrentExceptionUTF exceptionNumber=33554443 detailUTF=verifier unable to allocate native memory
Local fix
Problem summary
The issue is caused by a native memory allocation failure in the verifier.
Problem conclusion
This defect will be fixed in: 7.0.0 SR4 6.0.1 SR5 6.0.0 SR13 . The JVM has been updated to correctly handle the case where a native memory allocation fails in the verifier.
Temporary fix
Comments
APAR Information
APAR number
IV35580
Reported component name
J9 COMMON CODE
Reported component ID
620700127
Reported release
260
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-01-21
Closed date
2013-01-21
Last modified date
2013-01-21
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
J9 COMMON CODE
Fixed component ID
620700127
Applicable component levels
R260 PSY
UP
R600 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSNVBF","label":"Runtimes for Java Technology"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]
Document Information
Modified date:
21 February 2022