Page History

...

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

-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.port=8484
-Dcom.sun.management.jmxremote.rmi.port=8484
-Dcom.sun.management.jmxremote.ssl=false
-Djava.rmi.server.hostname=<IP_OR_HOSTNAME>

For remote access you need to specify 2 ports (that can be the same value) then that port needs to be opened in the firewall.

The java.rmi.server.hostname is also set in servoy (admin page/network settings) if rmi is used for the smart client. So if there 127.0.0.1 or localhost is defined. Then the above system property is overwritten again with that value that servoy configures when the web application starts up. Make sure that both settings have the same value. (If smart client is used with a public dns, try to use that public dns also for jmx internally)

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.

...