- 2 minutes to read

JMX, Scenarios, Business Value, ROI, Monitoring JMX, scenario, business value, ROI, use case 10. Can I monitor multiple JVMs per application server? - YES - common scenario: Single Windows/Linux server hosts multiple Java processes (3 Boomi Atoms, 5 Spring Boot microservices, 2 legacy J2EE apps = 10 JVMs on one server). Each JVM must have **uniq

10. Can I monitor multiple JVMs per application server?

10. Can I monitor multiple JVMs per application server?

YES - common scenario: Single Windows/Linux server hosts multiple Java processes (3 Boomi Atoms, 5 Spring Boot microservices, 2 legacy J2EE apps = 10 JVMs on one server). Each JVM must have unique JMX port.

Configuration:

  • Boomi Atom-1: JMX port 5002
  • Boomi Atom-2: JMX port 5003
  • Boomi Atom-3: JMX port 5004
  • Spring Boot Service-1: JMX port 9010
  • Spring Boot Service-2: JMX port 9011
  • etc.

Gateway configuration: Add 10 JVM endpoints to Gateway config file (host:port list). Gateway polls all 10 JVMs every 60 seconds, aggregates metrics, exposes via REST API. Nodinite Agent polls Gateway once, retrieves metrics for all 10 JVMs.

Benefits: Single Gateway instance monitors all 10 JVMs locally (no network latency), reduces firewall complexity (only Gateway→JVM communication required, not Agent→every JVM).

Limitations: JMX port conflicts (cannot reuse port 5002 for multiple JVMs on same server, must assign unique ports).