Monitoring using JMX

The host controller exposes MBeans over JMX, using the port 9999 (this is the same port used for the native management interface).

In order for JConsole, or another JMX client, to connect, the client must have additional JBoss remoting classes on the classpath. A script (jconsole.sh) is provided in the <install dir>/bin directory which will add these classes to the classpath when starting JConsole. Since the management port is secured, you will also need to provide the truststore containing the CA certificate being used by FAS, which is in the <install‑dir>/domain/configuration/security/default-trust directory.

1. Run the jconsole.sh script from the master FAS node (all on a single line):

<install dir>/bin/jconsole.sh ‑J‑Djavax.net.ssl.trustStore=<install dir>/domain/configuration/security/default‑trust/truststore.jks ‑J‑Djavax.net.ssl.trustStorePassword=<password>

where is the password for the truststore; by default, this is changeit.

2. Connect to the FAS host as a remote process:

The connection URL takes the form: service:jmx:remoting-jmx://<fas address>:9999, and the default Username and Password are admin and changeit.

3. When JConsole is connected, it displays the usual JVM information, the MBeans which are exposed, and an extra JBoss CLI tab.

From the MBeans tab, you can access the HotSpotDiagnostic and Threading MBeans:

You can use these to dump the heap (the file name is the first argument, and the file will be saved in the <install dir> directory), dump threads (these are dumped to an interactive window), find deadlocked threads, and so on.

The MBeans are available to applications hosted in a server process which calls ManagementFactory.getPlatformMBeanServer.

On the JBoss CLI tab, you can access the some of the same objects and their properties as you can from the CLI.

Right click the name of an object or attribute to access the operations availablee. In most cases, you will find it most convenient to change these using the CLI(see the Command Line Interface (CLI) section in the Management Interfaces article), which are more comprehensive; or the Management Console, for commonly changed settings (see the Management Console section in the Management Interfaces article), which is less comprehensive but more convenient.

Diagnostics

Fusion Application Server provides a script for collecting diagnostic information from a server for further offline investigation. Running it produces a ZIP file containing configuration and runtime information that might help you to diagnose problems:

1. Log on to the machine running FAS.

2. Change to the <install dir>/bin directory.

3. Run:

./jdr.sh

4. If prompted, enter an administrator username and password.

A ZIP file called sosreport-<host>-<date-time> is created in the <install dir>/bin directory, where <host> is the host name, and <date-time> is the local date and time in ISO format without separators (yyyyMMddHHmmss).

The ZIP file contains the following information:

• Configuration files (such as domain.xml and host.xml) and backups.

• Logs for the host controller, process controller, and each server process.

• Metadata about what modules are installed and what resources' dependencies are configured (module.xml files).

• Management interface configuration (configuration.json file).

• Other configuration files (such as thread dump information).

Core Dumps

In a production system, core dumps are normally disabled. To enable core dumps from FAS (for all users), edit the /etc/security/limits.conf file, and add the lines:

\* soft core unlimited

\* hard core unlimited

commenting out any existing lines relating to the core item.