Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
4.2.3
-
None
-
None
-
OS: IBM AIX 7.2
Java: openjdk version "11.0.4" 2019-07-16
OpenJDK Runtime Environment AdoptOpenJDK (build 11.0.4+11)
Eclipse OpenJ9 VM AdoptOpenJDK (build openj9-0.15.1, JRE 11 AIX ppc64-64-Bit Compressed References 20190717_292 (JIT enabled, AOT enabled)
OpenJ9 - 0f66c64
OMR - ec782f2
JCL - fa49279 based on jdk-11.0.4+11)OS: IBM AIX 7.2 Java: openjdk version "11.0.4" 2019-07-16 OpenJDK Runtime Environment AdoptOpenJDK (build 11.0.4+11) Eclipse OpenJ9 VM AdoptOpenJDK (build openj9-0.15.1, JRE 11 AIX ppc64-64-Bit Compressed References 20190717_292 (JIT enabled, AOT enabled) OpenJ9 - 0f66c64 OMR - ec782f2 JCL - fa49279 based on jdk-11.0.4+11)
Description
Under AIX 7.2 I have used the service wrapper. It creates the correct entry in /etc/inittab and also creates a wrapper.conf that looks fine (see attachement). Here the entry from the inittab:
NN_MyAgent1:2:once:/data/MyService/karaf/bin/NN_MyAgent1-service start
Starting karaf via the start-script from karaf/bin/ works as expected.
But when starting karaf via the service wrapper, the start fails with the following error shown in the wrapper.log (loglevel DEBUG):
DEBUG | wrapper | 2019/09/30 11:30:38 | Signal trapped. Details:DEBUG | wrapper | 2019/09/30 11:30:38 | Signal trapped. Details:DEBUG | wrapper | 2019/09/30 11:30:38 | signal number=20 (SIGCHLD), source="unknown"DEBUG | wrapper | 2019/09/30 11:30:38 | Received SIGCHLD, checking JVM process status.DEBUG | wrapper | 2019/09/30 11:30:38 | JVM process exited with a code of 1, setting the wrapper exit code to 1.ERROR | wrapper | 2019/09/30 11:30:38 | JVM exited while loading the application.INFO | jvm 1 | 2019/09/30 11:30:38 | Exception in thread "main" java/lang/ExceptionInInitializerErrorINFO | jvm 1 | 2019/09/30 11:30:38 | at java/lang/J9VMInternals.ensureError (java.base@9/Unknown Source:4294967295)INFO | jvm 1 | 2019/09/30 11:30:38 | at java/lang/J9VMInternals.recordInitializationFailure (java.base@9/Unknown Source:4294967295)INFO | jvm 1 | 2019/09/30 11:30:38 | at java/lang/ClassLoader.initializeClassLoaders (java.base@9/Unknown Source:4294967295)INFO | jvm 1 | 2019/09/30 11:30:38 | at java/lang/Thread.initialize (java.base@9/Unknown Source:4294967295)INFO | jvm 1 | 2019/09/30 11:30:38 | at java/lang/Thread.<init> (java.base@9/Unknown Source:4294967295)INFO | jvm 1 | 2019/09/30 11:30:38 | java/lang/RuntimeException: java.base specified more than once to --patch-moduleINFO | jvm 1 | 2019/09/30 11:30:38 | at jdk/internal/module/ModuleBootstrap.fail (java.base@9/Unknown Source:4294967295)INFO | jvm 1 | 2019/09/30 11:30:38 | at jdk/internal/module/ModuleBootstrap.decode (java.base@9/Unknown Source:4294967295)INFO | jvm 1 | 2019/09/30 11:30:38 | at jdk/internal/module/ModuleBootstrap.initModulePatcher (java.base@9/Unknown Source:4294967295)INFO | jvm 1 | 2019/09/30 11:30:38 | at jdk/internal/module/ModuleBootstrap.<clinit> (java.base@9/Unknown Source:4294967295)INFO | jvm 1 | 2019/09/30 11:30:38 | at java/lang/ClassLoader.initializeClassLoaders (java.base@9/Unknown Source:4294967295)INFO | jvm 1 | 2019/09/30 11:30:38 | at java/lang/Thread.initialize (java.base@9/Unknown Source:4294967295)INFO | jvm 1 | 2019/09/30 11:30:38 | at java/lang/Thread.<init> (java.base@9/Unknown Source:4294967295)DEBUG | wrapper | 2019/09/30 11:30:38 | JVM was only running for 0 seconds leading to a failed restart count of 1.
The entries in the wrapper.conf are looking ok for me, see attachement.
The Java used is an OpenJDK OpenJ9 Java 11 from AdoptJDK.