PI94670: _SETUPSDK1.8_64_BUNDLED.SH HAS 31 BIT JAVA_HOME which can resultin native out of storage

8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21

APAR status

• Closed as program error.

Error description

• /<WAS_HOME>/bin/sdk/_setupsdk1.8_64_bundled.sh contains:
  JAVA_HOME="$WAS_HOME"/java
  It should be:
  JAVA_HOME="$WAS_HOME"/java64
  If JVM max heap size is set high and/or storage below the line
  is limited and administrative script is ran (ex. wsadmin.sh,
  applyPTF.sh, and others in /bin directory), it may lead to
  native out of storage issue.
  Example #1:
  After WAS server was upgraded and restarted, Post-installer
  (applyPTF.sh) was invoked. However, the server terminated
  during startup with Java OOM errors. Javacore dump showed it
  was really native storage problem:
  Dump Event "systhrow" (00040000) Detail
  "java/lang/OutOfMemoryError" "native memory exhausted" received
  Javacore also showed it was running 31-bit Java even though WAS
  joblog showed the server was using 64-bit Java:
  JAVAVERSION JRE 1.8.0 z/OS s390-31
  User Region below the line was very limited due to IEFUSI exit
  in place.
  Example #2:
  wsadmin.sh script failed when JVM max heap size was changed
  from default to 1024M.
  JVMJ9VM015W error.  JVMJ9VM015W Initialization error for library
   j9gc29 (2): Failed to instantiate heap; 1G requested
  java -version showed 31-bit java was being used.
  

Local fix

• Upgrade to FixPack with the fix, or contact IBM Support.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  WebSphere Application Server for z/OS,      *
  *                  Version 8.5.5, 64-bit bundled Java 8        *
  *                  users.                                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: WebSphere Application Server for z/OS,  *
  *                      Version 8.5.5, incorrectly sets         *
  *                      JAVA_HOME for z/OS bundled Java 8 64-   *
  *                      bit to the 31-bit Java.                 *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  An internal script set the z/OS 64-bit JAVA_HOME variable to
  point to the 31-bit Java.
  

Problem conclusion

• The internal script has been corrected to set the z/OS 64-bit
  JAVA_HOME for the bundled Java 8 to point to the 64-bit bundled
  Java 8 directory.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.5.5.14.  Please refer to the Recommended Updates
  page for delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

Temporary fix

Comments

APAR Information

• 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

  WEBSPHERE FOR Z

• Fixed component ID

  5655I3500

Applicable component levels

• R850 PSY

     UP