Ad Widget

Collapse

Can't monitoring the JBoss application via Zabbix 3.0

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • crajapakshe
    Junior Member
    • Dec 2016
    • 1

    #1

    Can't monitoring the JBoss application via Zabbix 3.0

    Hi,

    I am using JBoss 7.1.1 final version. I configured Zabbix Java Gateway and tested some small java application it is work fine. I can see the Green colored status on Configuration> Hosts> Status tab.

    I have added following options to JAVA_OPTS:
    JAVA_OPTS="$JAVA_OPTS -Dcom.sun.management.jmxremote.port=4447 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -Djava.rmi.server.hostname=172.30.0.113"

    After add above configuration wont start the JBoss server. It is gave below error message.

    [root@jmx ~]# /jboss7/standalone/jboss.sh start
    Found 172.30.0.113 IP Address
    Starting server with ipaddress 172.30.0.113
    JBOSS_CMD_START = /jboss7/bin/standalone.sh --server-config=mytest.xml
    [root@jmx ~]# WARNING: Failed to load the specified log manager class org.jboss.logmanager.LogManager
    Exception in thread "main" java.lang.ExceptionInInitializerError
    at org.jboss.as.server.Main.main(Main.java:73)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:57)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:606)
    at org.jboss.modules.Module.run(Module.java:260)
    at org.jboss.modules.Main.main(Main.java:291)
    Caused by: 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: 60)
    at org.jboss.logmanager.log4j.BridgeRepositorySelecto r.<clinit>(BridgeRepositorySelector.java:42)
    ... 7 more


    Anyone have this issues?
    Please help.
    Thanks.
  • elias.oajr
    Junior Member
    • Jan 2017
    • 1

    #2
    Hello!
    I had the same problem, this is a logging problem in jboss 7.x.x.
    To solve you can add these two lines in your jboss standalone.conf file.

    At the begging of the file add the following line:
    # Added for logging problem
    JBOSS_MODULES_SYSTEM_PKGS="org.jboss.logmanager"


    At the end of the file add the following to solve the logging problem:
    # Added for logging problem
    JAVA_OPTS="$JAVA_OPTS -Djava.util.logging.manager=org.jboss.logmanager.Lo gManager -Xbootclasspath/p:$JBOSS_HOME/modules/org/jboss/logmanager/main/jboss-logmanager-1.2.2.GA.jar -Xbootclasspath/p:$JBOSS_HOME/modules/org/jboss/logmanager/log4j/main/jboss-logmanager-log4j-1.0.0.GA.jar -Xbootclasspath/p:$JBOSS_HOME/modules/org/apache/log4j/main/log4j-1.2.16.jar"


    I await good news!

    Elias Junior

    Comment

    Working...