JMX Notification Configuration

The JMX Monitoring configuration page can be found under Configurations → <config-name> → Monitoring.

From the Monitoring page, select the tab labelled JMX:

The JMX page allows you to specify the time between notifications, how notifications will be delivered, and the MBeans which will be included within the message.

By default, both JMX and AMX start disabled.

To enable JMX Monitoring for the JVM, select Enabled:

To enable AMX (recommended), go to General monitoring page and select AMX Enabled:

To enable JMX Monitoring for the JVM via asadmin, use the command:

To configure the frequency of logged data, enter both the intended frequency of logs and the unit of time.

For example, to log every 30 milliseconds:

To configure the data logging frequency via asadmin, use the command:

Before you receive notifications from your chosen notifier, please ensure that you have configured the notification service.

To select notifiers to use for JMX Monitoring, hold the CTRL or SHIFT key to select multiple notifiers, and then click Add >.

For each notifier you wish to enable use the command:

Available Notifiers can be viewed on the notifiers page.

By default, JMX will output an empty message as there are no MBeans configured.

To add an MBean to the monitoring service, click Add Attribute on the Monitored Attributes table at the bottom of the page:

You can now add your monitoring attributes to the notification service using the following values:

MBean attribute names and domain names can be discovered using JConsole, JVisualVM, Java Mission Control or other programs. To browse available MBean attributes, after enabling JMX and AMX in the admin console, connect to your Payara Server Enterprise instance from your chosen program:

From here, to find an MBean, select the MBeans tab to view all MBeans on the server. If you have enabled "HIGH" monitoring for all components along with JMX monitoring you should be able to see the following files:

From here you can search MBeans for attributes which you wish to monitor. Once you have located an MBean attributes you can add it to the DAS using the given object name (or, if not present, the type, name, and location of the MBean in the following format):

For example, to monitor the HeapMemoryUsage of the MBean on the DAS with a domain (Object Name) of java.lang:type=Memory, you would enter:

Click the Save button at the top of the page to save and exit. If you have entered all values correctly, you should see a message via your chosen notifier with the MBeans contents:

Via the logs:

Via HipChat:

To add a attribute via asadmin, use the command:

So to replicate the above attributes, use the command: