APAR status
Closed as program error.
Error description
Error Message: Shutdown of application, in stderr the following was seen: Assertion failed: 0, file .../Assert.cpp, line 72 . Stack Trace: {libpthreads.a}{pthread_kill} {libpthreads.a}{_p_raise} {libc.a}{raise} {libc.a}{abort} {libc.a}{__assert_c99} {libj9jit29.so}{assumeDontCallMeDirectlyImpl__FPCciN21Pcb} {libj9jit29.so}{fatal_assertion__2TRFPCciN21e} {libj9jit29.so}{badILOpEvaluator__Q2_3OMR13TreeEvaluatorFPQ2_2TR 4NodePQ2_2TR13CodeGenerator} {libj9jit29.so}{evaluate__Q2_3OMR13CodeGeneratorFPQ2_2TR4Node} {libj9jit29.so}{doInstructionSelection__Q2_2J913CodeGeneratorFv} {libj9jit29.so}{performInstructionSelectionPhase__Q2_3OMR12CodeG enPhaseFPQ2_2TR13CodeGeneratorPQ2_2TR12CodeGenPhase} {libj9jit29.so}{performAll__Q2_3OMR12CodeGenPhaseFv} {libj9jit29.so}{generateCode__Q2_3OMR13CodeGeneratorFv} {libj9jit29.so}{compile__Q2_3OMR11CompilationFv} {libj9jit29.so}{compile__Q2_2TR28CompilationInfoPerThreadBaseFP1 0J9VMThreadPQ2_2TR11CompilationP17TR_ResolvedMethodR11TR_J9VMBas eP19TR_OptimizationPlanRCQ2_2TR16SegmentAllocator} {libj9jit29.so}{wrappedCompile__Q2_2TR28CompilationInfoPerThread BaseFP13J9PortLibraryPv} {libj9prt29.so}{omrsig_protect} {libj9jit29.so}{compile__Q2_2TR28CompilationInfoPerThreadBaseFP1 0J9VMThreadP21TR_MethodToBeCompiledRQ2_2J917J9SegmentProvider} {libj9jit29.so}{processEntry__Q2_2TR24CompilationInfoPerThreadFR 21TR_MethodToBeCompiledRQ2_2J917J9SegmentProvider} {libj9jit29.so}{processEntries__Q2_2TR24CompilationInfoPerThread Fv} {libj9jit29.so}{run__Q2_2TR24CompilationInfoPerThreadFv} {libj9jit29.so}{protectedCompilationThreadProc__FP13J9PortLibrar yPQ2_2TR24CompilationInfoPerThread} {libj9prt29.so}{omrsig_protect} {libj9jit29.so}{compilationThreadProc__FPv} {libj9thr29.so}{thread_wrapper} {libpthreads.a}{_pthread_body} The frame with "badILOpEvaluator()" is the key indicator that the problem this APAR describes has occurred. . This problem can occur on any platform when using the J9 JVM
Local fix
The problem can be avoided by using the following java command line option: -Xjit:disableAutoSIMD A performance impact might be seen if your application is written in a way where AutoSIMD finds a lot of optimization opportunities, but in most large server side applications the effect will be very small.
Problem summary
The problem occurs when a section of code is optimized by autoSIMD which should have been marked as invalid for autoSIMD. This is due to a failure to correctly check if all criteria for autoSIMD are present.
Problem conclusion
The JVM has been updated to perform proper checks before autoSIMD optimizations are applied. . This APAR will be fixed in the following Java Releases: 8 SR5 FP26 (8.0.5.26) . Contact your IBM Product's Service Team for these Service Refreshes and Fix Packs. For those running stand-alone, information about the available Service Refreshes and Fix Packs can be found at: https://www.ibm.com/developerworks/java/jdk/
Temporary fix
Comments
APAR Information
APAR number
IJ11150
Reported component name
JIT
Reported component ID
620700124
Reported release
130
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2018-11-07
Closed date
2018-11-07
Last modified date
2018-11-07
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
JIT
Fixed component ID
620700124
Applicable component levels
[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSC9HBA","label":"Just In Time (JIT) Compiler"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"130","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
07 November 2018