Jboss 7.1 monitoring

Using the JMX interface in SAM you can monitor things like java heap, garbage collection, free memory, etc.

You must enable the JMX interface on the windows server and generate an id/password for SAM to use.

It is easier to test connectivity using jconsole before pointing SAM at it.

Here are some bits of info on this.

Java Arguments

For enabling remote JMX monitoring, the following Java arguments will be used:

-Djava.rmi.server.hostname=192.168.0.236
This line indicates the IP address the RMI server will use. Type your server IP address here.

-Dcom.sun.management.jmxremote
This line enables remote JMX monitoring.

-Dcom.sun.management.jmxremote.port=8686
This line indicates which port the JMX module will use to accept JMX connections.

-Dcom.sun.management.jmxremote.ssl=false
This line indicates whether or not SSL is used.

-Dcom.sun.management.jmxremote.authenticate=true
This line indicates whether or not authentication is used. Use of authentication is recommended. If you do not want to use authentication, you should change the value to false.

-Dcom.sun.management.jmxremote.password.file=c:\jmxremote.password
This line indicates where the passwords file is stored. Do not add this line if you are not using authentication.

-Dcom.sun.management.jmxremote.access.file=c:\jmxremote.access
This line indicates where the access file is stored. Do not add this line if you are not using authentication.

More information can be found at the following website: http://docs.oracle.com/javase/1.5.0/docs/guide/management/agent.html.

Configuring a Standalone Java Virtual Machine

Windows:

1. Download the JDK from the Oracle website: http://www.oracle.com/technetwork/java/javase/downloads/index.html (tested on JDK 1.7.0, update version 3).

2. Install the JDK.

3. On the license agreement page, read and accept the license and then click Next.

4. Click Change to change the installation directory to C:\Program Files\Java\jdk1.7.0_3, and then click OK.

5. Click Next.

6. Click Finish to exit from the installer.

7. Add a variable to the system with its path pointing to the JDK installation folder.

For example:

Variable name: JAVA_HOME
Variable value: C:\Program Files\Java\jdk1.7.0_3

Note: If you want to run Java commands from the command line, you should add the JDK installation path to the PATH variable.

If you plan to use JMX authentication, follow steps 8-12.

8. Navigate to the %JAVA_HOME%\jre\lib\management folder.

9. Rename the jmxremote.password.template file to jmxremote.password. Edit jmxremote.password by replacing/adding its content with the following:

samuser somepasswd

Where samuser is the user for the JVM monitored from SAM and somepasswd – is the password.

10. Edit jmxremote.access by replacing/adding its content with the following:

samuser readonly

Where samuser is user for the JVM monitored and readonly – gives this read only permissions.

11. Copy jmxremote.access and jmxremote.password to a folder, for example c:\jmxremote\.

12. Grant access to the jmxremote.password file only for the Administrator. To grant access only for the Administrator, refer to this topic at the following location: http://download.oracle.com/javase/6/docs/technotes/guides/management/security-windows.html

kashif091,

In addition to Jfrazier's input, check out the Configure Java application servers and JVMs for SAM monitoring section in the SAM Template Reference.  

Additional info is available at:

• JBoss (JMX) template
• Understanding Java Remote JMX - SAM Template Config