- 2 minutes to read

JMX, FAQ, Troubleshooting, Common Questions JMX, FAQ, troubleshooting, common questions 2. How do I enable JMX remote monitoring on my Java application?

2. How do I enable JMX remote monitoring on my Java application?

2. How do I enable JMX remote monitoring on my Java application?

Add JVM arguments when starting Java application:

-Dcom.sun.management.jmxremote
-Dcom.sun.management.jmxremote.port=5002
-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.ssl=false
-Dcom.sun.management.jmxremote.local.only=false
-Djava.rmi.server.hostname=192.168.1.100

Configuration details:

  • port=5002 - JMX listening port (choose unused port, common: 5002, 9010, 8686)
  • authenticate=false - Disable authentication (use for internal monitoring, enable for production security)
  • ssl=false - Disable SSL (use for internal monitoring, enable for production security)
  • local.only=false - Allow remote connections (required for Nodinite Gateway)
  • hostname=192.168.1.100 - Set to server IP address (prevents RMI hostname lookup issues)

For Boomi Atoms: Configure JMX port in Boomi Atom Management console → Properties → JMX Settings → Port (default 5002).

For Spring Boot: Add to application.properties:

spring.jmx.enabled=true
management.endpoints.jmx.exposure.include=*

Security recommendation: For production, enable authentication (-Dcom.sun.management.jmxremote.authenticate=true) + SSL, configure password file, use firewall rules to restrict JMX port access to Gateway server only.

See all FAQs: [Troubleshooting Overview][]