Child pages
  • Monitoring Servoy with JMX
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Java Management Extensions (JMX) provides a way to manage and monitor resources dynamically at runtime. These resources are represented by objects called Managed Beans (MBeans). The MBeans are registered to the MBean Server from where they can be accessed via any JMX client, like JConsole for example.

Servoy supports datasource monitoring using JMX, that is monitoring the data servers.

Each enabled/active data server is exposed by the Application Server as an MBean in the JMX domain name com.servoy.datasource. For each data server the MBean is exposed with the configuration details of the server.

To enable connecting to the JMX bean of the ApplicationServer, a java option needs to be added to the startup commands:

-Dcom.sun.management.jmxremote

There is also a GaugeMonitor per server, named NumActiveMonitor_{serverName}, to monitor active connections and get notifications when limits are passed. The limits can be modified via the attributes. Notifications are pushed to the JMX client.

The JMX interface can be used with any JMX client. Java comes with a simple JMX client, called jconsole, which is a simple GUI to configure the attributes and show the monitoring data. The jconsole is found in the bin folder of the installed Java JDK.

  • No labels