How to setup and access jconsole for Jboss jboss-eap-6.1 for Jboss beans monitoring

[subit_cog]

I am using jboss-eap-6.1 and I want to monitor the beans as well as CPU and Memory.

I failed  to connect the server remotely from a windows machine to the Linux machine where Jboss is installed.

Although I am able to connect other java processes using Java VisualVM , but it's not sufficient enough.

I have attached the screenshots for the Jconsole issues. Please refer that. I have tried 3 ports in the jconsole i.e. 9999, 4447, 9990

I tried to add the below parameters to the standalone.conf , but always I found the below errors and I have not found any resolution yet although , I have searched in many links and done alot of changes accordingly.

So please suggest me activation steps for jcosole or any other alternate way to monitor.

Please find below few details related to my Jboss server

JBOSS logger system property (This is a generic issue that comes up often, indicating that the jboss system property is not set).

11:38:03,994 INFO  [org.jboss.modules] (main) JBoss Modules version 1.2.0.Final-redhat-1

1. 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:61)

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

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

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

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

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

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

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

or

WARNING: Failed to load the specified log manager class org.jboss.logmanager.LogManager

Jul 21, 2015 12:14:03 PM org.jboss.msc.service.ServiceContainerImpl <clinit>

INFO: JBoss MSC version 1.0.4.GA-redhat-1

Jul 21, 2015 12:14:03 PM org.jboss.as.server.ApplicationServerService start

INFO: JBAS015899: JBoss EAP 6.1.0.GA (AS 7.2.0.Final-redhat-8) starting

Jul 21, 2015 12:14:04 PM org.jboss.as.controller.AbstractOperationContext executeStep

ERROR: JBAS014612: Operation ("parallel-extension-add") failed - address: ([])

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

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

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

        at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:322)

        at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:229)

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

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

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

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

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

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

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

Possible Resolution

We added “JAVA_OPTS=" $JAVA_OPTS -Djava.util.logging.manager=org.jboss.logmanager.LogManager" “ in the JVM arguments but the error still persists.

I

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

JVM Arguments

JBOSS_MODULES_SYSTEM_PKGS="org.jboss.logmanager,org.jboss.logmanager.config,org.jboss.logmanager.errormanager,org.jboss.logmanager.filters,org.jboss.logmanager.formatters,org.jboss.logmanager.handlers"

JAVA_OPTS="$JAVA_OPTS -Dcom.sun.management.jmxremote.port=8998"

JAVA_OPTS="$JAVA_OPTS -Dcom.sun.management.jmxremote.authenticate=false"

JAVA_OPTS="$JAVA_OPTS -Dcom.sun.management.jmxremote=true"

JAVA_OPTS="$JAVA_OPTS -Dcom.sun.management.jmxremote.ssl=false"

JAVA_OPTS="$JAVA_OPTS -Djboss.platform.mbeanserver"

JAVA_OPTS="$JAVA_OPTS -Djava.rmi.server.hostname=<ip of my server>"

JAVA_OPTS="$JAVA_OPTS -Djboss.modules.system.pkgs=org.jboss.logmanager"

JAVA_OPTS="$JAVA_OPTS -Djava.util.logging.manager=org.jboss.logmanager.LogManager -Xbootclasspath/p:/app/appserver/jboss/jboss-eap-6.1/modules/system/layers/base/org/jboss/logmanager/main/jboss-logmanager-1.4.0.Final-redhat-1.jar  -Xbootclasspath/p:/app/appserver/jboss/jboss-eap-6.1/modules/system/layers/base/org/jboss/log4j/logmanager/main/log4j-jboss-logmanager-1.0.1.Final-redhat-2.jar"

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

echo $PATH

----------------------

/app/appserver/jboss/jboss-eap-6.1/bin:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.85.x86_64/lib:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.85.x86_64/bin:/usr/lib/jvm/jre-1.7.0-oracle.x86_64/bin:/app/appserver/jboss/jboss-eap-6.1/modules/system/layers/base/org/jboss/log4j/logmanager/main/log4j-jboss-logmanager-1.0.1.Final-redhat-2.jar:/app/appserver/jboss/jboss-eap-6.1/modules/system/layers/base/org/jboss/logmanager/main/jboss-logmanager-1.4.0.Final-redhat-1.jar:/usr/lib64/qt-3.3/bin:/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin

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

echo $JBOSS_HOME

/app/appserver/jboss/jboss-eap-6.1

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

echo $JAVA_HOME

/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.85.x86_64

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

[mayerw01]

How did you start your AS? Did this issue exist from the very beginning or did you change something in between?

Can you access this AS locally via jconsole.sh?

Did you check if this problem comes up on a new installation as well?

Did you also try the suggestion in this blog? Cannot start AS 7.1 Final LogManager error

[subit_cog]

Thanks for your response.

Please find below the details , you asked

How did you start your AS? Did this issue exist from the very beginning or did you change something in between?

I start using standalone.sh file

Can you access this AS locally via jconsole.sh?

Yes, but local Linux machine does not have x-window graphics configured. But jconsole running there.

Did you check if this problem comes up on a new installation as well?

Yes, same problem is there in new fresh installation too.

Did you also try the suggestion in this blog? Cannot start AS 7.1 Final LogManager error

I followed the suggestion in that link. I added -logmodule org.jboss.logmanager to the program arguments before org.jboss.as.standalone. All the errors are gone. Server starting up perfectly with all JMX parameters as given below.

But still I am not able to connect remotely using Jconsole. The older issues still exists while connecting back. And this time, I am not able to track even that, what is the error.

   JAVA_OPTS="$JAVA_OPTS -Dcom.sun.management.jmxremote.port=9999"

   JAVA_OPTS="$JAVA_OPTS -Dcom.sun.management.jmxremote.authenticate=false"

   JAVA_OPTS="$JAVA_OPTS -Dcom.sun.management.jmxremote=true"

   JAVA_OPTS="$JAVA_OPTS -Dcom.sun.management.jmxremote.ssl=false"

   JAVA_OPTS="$JAVA_OPTS -Djboss.platform.mbeanserver"

   JAVA_OPTS="$JAVA_OPTS -Djava.rmi.server.hostname=xx.xx.xx.xx"

   JAVA_OPTS="$JAVA_OPTS -Djboss.modules.system.pkgs=org.jboss.logmanager"

  JAVA_OPTS="$JAVA_OPTS -Djava.util.logging.manager=org.jboss.logmanager.LogManager

Thanks,

Subit Das

[mayerw01]

Are you sure that the connection is not rejected by the firewall?

Do you get any entries in the JConsole:Output window?