PH39665: JAVA 11 / WEBENAB.LIBERTY VERSION 21.0.0.4 NOT ABLE TO START

APAR status

• Closed as program error.

Error description

• VMJ9VM007E Command-line option unrecognised:
  jdk.management.agent/jdk.internal.agent=ALL-UNNAMED
  Unable to create Java Virtual Machine.
  /java -version
  
  
  openjdk version ?11.0.8? 2020-07-14
  
  
  OpenJDK Runtime Environment 11.0.8.0-IBM (build 11.0.8+10)
  
  
  Eclipse OpenJ9 VM 11.0.8.0-IBM (build openj9-0.21.0, JRE 11
  OS/400 ppc64-64-Bit Compressed References 20210119_000000
  (JIT
  enable
  d, AOT enabled)
  
  
  OpenJ9  - 34cf4c0
  
  
  OMR   - 113e542
  
  
  JCL   - 95bb504 based on jdk-11.0.8+10)
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server Liberty on IBM i using Java 11       *
  ****************************************************************
  * PROBLEM DESCRIPTION: WebSphere Liberty server fails to start *
  *                      on IBM i running with Java 11           *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Currently, WebSphere Liberty is unable to start on the IBM i
  platform running on Java 11.
  When trying to start a Liberty server in Java 11, the server
  refuses to start and a message, like the following, can be seen
  in the console.log file for that Liberty server:
  
  JVMJ9VM007E Command-line option unrecognised:
  java.base/sun.security.action=ALL-UNNAMED
  Unable to create Java Virtual Machine.
  
  This is due to the Java Modules changes that came out in Java 9.
  A file called java9.options was added to Liberty, in
  ../wlp/lib/platform/java, as a single place to collect any
  required Java Module deviations necessary for it to run. In this
  file, the format of the entries looks like this:
  
  --add-opens
  java.base/java.util=ALL-UNNAMED
  --add-opens
  java.base/java.lang=ALL-UNNAMED
  ...
  
  On most platforms, when starting Liberty, the java9.options file
  is read in and these arguments are passed in during the starting
  of the JVM. According to Oracle, it is not necessary to add an
  equals sign = between the key and value pairings.
  
  However, on IBM i, we start the JVM using JNI where it is
  required to have an equals sign between the key and value pair
  specified in long format (i.e. --add-opens=value). Since the
  java9.options file is common across all platforms, it does not
  make sense to modify that as that could have unintentional side
  effects on other platforms.
  

Problem conclusion

• The QWLPSTRSVR program, responsible for starting Liberty on IBM
  i, was changed to process those key value pairs, sent in by the
  server command, and insert the = sign as necessary.
  This will allow WebSphere Liberty servers to properly start on
  IBM i when running with Java 11.
  
  The fix for this APAR is currently targeted for inclusion in fix
  pack 21.0.0.11.  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

  WAS LIBERTY COR

• Fixed component ID

  5725L2900

Applicable component levels