KB Article #170387
Monitoring JVM used in Integrator with jmxremote
Problem
- JVM loaded by Integrator in some Processing Engines has to be monitored
Resolution
- update $CORE_LOCAL/config/environment.dat with these lines for each PE:
- Procengine_JMS:
JAVA_TOOL_OPTIONS=-Djavax.management.builder.initial= -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.port=50003
Note:
- this was an example for a PE (JMS), and you have to keep in mind next conditions:
- not all PE run JVM (FTP doesn't do it, as an example);
- even you have defined forĀ all PE you have, not all ports will be on listening when PE start. On my installation, PE for JMS and WS passed well in listening, when JDBC, Sentinel, etc didn't yet pass in listen. Cause: not all API were designed identically. JMS and WS are pooling the target server, when the others make connections in asyncronous mode (at demand).
- mandatory: ports have to be defined separately: so 50003 for JMS, 50005 for WS, etc.