JBoss refuses to run as Install4j service due to earlier logging configuration

Question

I am trying to use Install4j's Service Launcher to deploy a bundled JBoss EAP 6.1 with our application. JBoss is refusing to start because:

java.lang.RuntimeException: JBAS014670: Failed initializing module org.jboss.as.logging
...
Caused by: java.util.concurrent.ExecutionException: java.lang.IllegalStateException: JBAS011592: The logging subsystem requires the log manager to be org.jboss.logmanager.LogManager. The subsystem has not be initialized and cannot be used. To use JBoss Log Manager you must add the system property "java.util.logging.manager" and set it to "org.jboss.logmanager.LogManager"

I already have this java.util.logging.manager system property set but I believe Install4j's wrapper is somehow initializing a JRE-wide logging facility prior to JBoss getting a chance. So JBoss just refuses to run.

Please see this JBoss issue where users with the TanukiSoftware wrapper face a similar problem. Is there any way of disabling this earlier initialization in the Install4j service launcher so that JBoss will run?

Answer 1

In install4j 5.1.8, there will be a system property "install4j.noLoggingFix" that prevents the initialization of the logging system. Please contact support@ej-technologies.com to get an interim build with this feature.