2 Replies Latest reply on May 1, 2015 10:49 PM by thomas.frey

    JMX monitoring of domain controlled servers

    thomasmosigfrey

      Hi

       

      I use WildFly 8.2 in domain mode and have configured a set of server groups with their servers.

      The wildfly jmx module is active and remote access successfully opened and accessed at the domain controller.

       

      BUT:

      Unfortunately I cannot open a JMX connection to the controlled servers for monitoring.

      So I tried the classical JMX options as JVM parameters for these server JVMs (copied from the )

       

      -Dcom.sun.management.jmxremote.rmi.port=3333

      -Dcom.sun.management.jmxremote.port=3333

      -Dcom.sun.management.jmxremote.ssl=false

      -Dcom.sun.management.jmxremote.authenticate=false

       

      The result is an error at the logging module and the wrong PermSize parameters.

      To me it looks like a wrong composition of the start command built by the Host Controller.

       

      [Host Controller] 11:02:47,900 INFO  [org.jboss.as.host.controller] (ProcessControllerConnection-thread - 2) JBAS010926: Unregistering server server-one

      [Host Controller] 11:03:44,452 INFO  [org.jboss.as.host.controller] (XNIO-1 task-1) JBAS010923: Stopping server server-one

      [Host Controller] 11:03:44,457 INFO  [org.jboss.as.host.controller] (XNIO-1 task-1) JBAS010922: Starting server server-one

      11:03:44,464 INFO  [org.jboss.as.process.Server:server-one.status] (ProcessController-threads - 5) JBAS012017: Starting process 'Server:server-one'

      [Server:server-one] WARNING: Failed to load the specified log manager class org.jboss.logmanager.LogManager

      [Server:server-one] Exception in thread "main" java.lang.IllegalStateException: The LogManager was not properly installed (you must set the "java.util.logging.manager" system property to "org.jboss.logmanager.LogManager")

      [Server:server-one]     at org.jboss.logmanager.Logger.getLogger(Logger.java:61)

      [Server:server-one]     at org.jboss.as.server.DomainServerMain.main(DomainServerMain.java:86)

      [Server:server-one]     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

      [Server:server-one]     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)

      [Server:server-one]     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

      [Server:server-one]     at java.lang.reflect.Method.invoke(Method.java:483)

      [Server:server-one]     at org.jboss.modules.Module.run(Module.java:312)

      [Server:server-one]     at org.jboss.modules.Main.main(Main.java:460)

      [Server:server-one] Java HotSpot(TM) 64-Bit Server VM warning: ignoring option PermSize=256m; support was removed in 8.0

      [Server:server-one] Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0

      11:03:45,292 INFO  [org.jboss.as.process.Server:server-one.status] (reaper for Server:server-one) JBAS012010: Process 'Server:server-one' finished with an exit status of 1

      [Host Controller] 11:03:45,298 INFO  [org.jboss.as.host.controller] (ProcessControllerConnection-thread - 2) JBAS010926: Unregistering server server-one

       

      Any idea to fix that? As I said: the goal is to retrieve monitoring data via JMX from the controlled hosts.

       

      Cheers and many thanks in advance

       

      Thomas

        • 1. Re: JMX monitoring of domain controlled servers
          craigmjones96

          Any luck with this? Im trying to do the same and hit the same problems

          • 2. Re: JMX monitoring of domain controlled servers
            thomas.frey

            Hi Craig

             

            there are good news and it's a little embarrassing. Again thinking before acting helped :-).

            As WIldfly starts to concentrate many of it's services at a few port numbers (http/https) the jmx queryies can simply be directed to these ports after the jmx subsystem is activated with the use-management-endpoint property set to false. I started to write a nagios plugin that can be used as a conveniant tool for JMX extracts as well. It will be found a sourceforge soon.

             

            I hope this answer helps :-)

             

            Cheers

             

            Thomas