Liberty JVM Server startup fails with abend 4094 reason code 00000014
I am running CICS Transaction Server for z/OS (CICS TS) V5.3 on two LPARs. I can start a Liberty JVM server on the first LPAR. But on the second LPAR, why does the Liberty JVM server fail at startup with a abend 4094 with return code 00000014?
In reviewing the STDERR report, the Java stack shows that the JVM server is failing with the 0C4 abend which is occurring in native method ntv_loadUnauthorized which is within the program NativeServiceTracker.java.
This module has to do with the angel process connection during the initialization of the Libery JVM server. So to verify the Angel process is running on the LPAR, the following command was entered:
F BBGZANGL,VERSION
But this indicated that the angel was NOT active. By default the Liberty JVM server will try to connect to the angel process during its start up, unless you specify WLP_ZOS_PLATFORM=FALSE within the JVM profile. This will prevent the Liberty JVM server from connecting to the angel process and will alleviate the abend. This is a workaround if you do not plan to start an angel process on the LPAR, or until one can be started.
Shayla Robinson
IBM CICS Level2 Support
Another point to add...
Setting WLP_ZOS_PLATFORM=FALSE effectively turns 'OFF' security for that JVM server - it can no longer communicate with the WebSphere angel process (which would otherwise perform the authorised calls to SAF). However, this technique is useful in development, test and POC systems as it allows you to run more than one Liberty JVM server per CICS region.
Ivan Hargreaves
IBM CICS Java and Liberty Architect