IBM support has me adding this to the tomcat java environment properties:
IJO="$IJO -Xjit:noResumableTrapHandler" # set required java option
It has resolved the abends, still working with them to find out the why's, and why did this behavior start with JAVA 7.1. I will report back additional information as I receive it.
S422-1A0
Re: S422-1A0
Just to close the loop on this issue, after talking with IBM, there have been changes in JAVA V7.1. Here is their explanation:
beginning with java7, when -Xaggressive is specified, the jit compiler
will generate code which can generate these 0c7's if the source
program causes NullPointerException, ArrayIndexOutOfBoundsException,
or an ArithmeticException to be thrown. With 7.1, the jit uses the
compare and trap instructions by default.
We have a customized set of LE runtime options that were interfering, so I am overriding those specific ones in the TOMCAT Proc:
//TOMCAT EXEC JVMPROC,
// LEPARM='TERMTHDACT(TRACE,CESE,00000096),ERRCOUNT(0)',
// JAVACLS='org.apache.catalina.startup.Bootstrap',
// ARGS='start'
beginning with java7, when -Xaggressive is specified, the jit compiler
will generate code which can generate these 0c7's if the source
program causes NullPointerException, ArrayIndexOutOfBoundsException,
or an ArithmeticException to be thrown. With 7.1, the jit uses the
compare and trap instructions by default.
We have a customized set of LE runtime options that were interfering, so I am overriding those specific ones in the TOMCAT Proc:
//TOMCAT EXEC JVMPROC,
// LEPARM='TERMTHDACT(TRACE,CESE,00000096),ERRCOUNT(0)',
// JAVACLS='org.apache.catalina.startup.Bootstrap',
// ARGS='start'