5 Replies Latest reply on Sep 2, 2019 9:30 AM by galder.zamarreno

    Jolokia in Infinispan Server

    ninjasftw

      Hi,

       

      I'm currently investigating building out an Infinispan cluster (infinispan-server-8.2.6.Final) and am looking at the monitoring options for it.

      Most of my other systems use Jolokia to expose the jmx interfaces.

       

      When I install jolokia as an agent I get and error saying that the logging subsystem requires the log manager to be org.jboss.logmanager.LogManager

      java.lang.RuntimeException: WFLYCTL0079: Failed initializing module org.jboss.as.logging

        at org.jboss.as.controller.extension.ParallelExtensionAddHandler$1.execute(ParallelExtensionAddHandler.java:115)

        at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:890)

        at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:659)

        at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:370)

        at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1344)

        at org.jboss.as.controller.ModelControllerImpl.boot(ModelControllerImpl.java:459)

        at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:387)

        at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:349)

        at org.jboss.as.server.ServerService.boot(ServerService.java:392)

        at org.jboss.as.server.ServerService.boot(ServerService.java:365)

        at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:299)

        at java.lang.Thread.run(Thread.java:745)

      Caused by: java.util.concurrent.ExecutionException: java.lang.IllegalStateException: WFLYLOG0078: 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"

        at java.util.concurrent.FutureTask.report(FutureTask.java:122)

        at java.util.concurrent.FutureTask.get(FutureTask.java:192)

        at org.jboss.as.controller.extension.ParallelExtensionAddHandler$1.execute(ParallelExtensionAddHandler.java:107)

        ... 11 more

       

       

      Having a look around I found this bug report saying that you had to force load the log manager module

      How to implement compatibility of the Jolokia JVM agent with org.jboss.logmanager.LogManager loaded form JBoss modules ·…

       

      I set the following options after downloading a copy of wildfly 10 to get hold of the logmanager library

       

      JAVA_OPTS="$JAVA_OPTS -javaagent:/apps/jolokia/jolokia.jar=port=9080 -Xbootclasspath/p:/apps/wildfly-10.1.0.Final/modules/system/layers/base/org/jboss/logmanager/main/jboss-logmanager-2.0.4.Final.jar"

      however it still reports

      =========================================================================

       

        JBoss Bootstrap Environment

       

        JBOSS_HOME: /apps/infinispan-server-8.2.6.Final

       

        JAVA: /apps/java/current//bin/java

       

        JAVA_OPTS: -javaagent:/apps/jolokia/jolokia.jar=port=9080 -Djava.util.logging.manager=org.jboss.logmanager.LogManager -Xbootclasspath/p:/apps/wildfly-10.1.0.Final/modules/system/layers/base/org/jboss/logmanager/main/jboss-logmanager-2.0.4.Final.jar  -server  -server -Xms64m -Xmx512m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true

       

      =========================================================================

       

      I> No access restrictor found, access to any MBean is allowed

      Jolokia: Agent started with URL http://127.0.0.1:9080/jolokia/

      17:25:47,817 INFO  [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final

      java.lang.IllegalStateException: The LogManager was not properly installed (you must set the "java.util.logging.manager" system property to "org.jboss.logmanager.LogManager")

        at org.jboss.logmanager.Logger.getLogger(Logger.java:57)

        at org.jboss.as.server.Main.main(Main.java:87)

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

        at java.lang.reflect.Method.invoke(Method.java:498)

        at org.jboss.modules.Module.run(Module.java:329)

        at org.jboss.modules.Main.main(Main.java:507)

       

      Any help would be appreciated as I like the product but without an easy way to monitor its going to be hard to implement. 

      I don't currently utilise RHQ/JON so I don't really want to have to deploy it just for this.

       

      Thanks