OPDK 4.16.1.2 - Setup JMX Monitoring ports through firewall

Not applicable

JMX has a nasty requirement of requiring a second ephemeral port when establishing a connection and defaults to using any open port, which is being blocked by our firewall between our monitoring server and an Edge component, in this case an Edge Message Processor on port 1101.

Is there a configuration option I can specify to set the JMX second port instance? If this was a standard Java management process, I would use -Dcom.sun.management.jmxremote.rmi.port=1101

I have editied

/opt/apigee/customer/application/message-processor.properties to include

conf/communication.properties+com.sun.management.jmxremote.rmi.port=1101

But that did not make the secondary JMX port selected to be a known firewall friendly port.

0 0 310
0 REPLIES 0