JMX doesn't give the information you want

[#1]

we are doing some tests with a on-premise installation and are trying to monitor the system through JMX. However, the documentation is... well.. mostly just wrong.

The part described here: http://docs.apigee.com/private-cloud/latest/how-monitor tells us to enable JMX by adding the lines

-Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=1099 
-Dcom.sun.management.jmxremote.local.only=false  
-Dcom.sun.management.jmxremote.authenticate=false 
-Dcom.sun.management.jmxremote.ssl=false

But when I do this, the MS fails to start because it's trying to connect to a port that is already in use.

Turns out, it already started JMX. After a lot of trial and error I can make a connection from JConsole.

I cannot however get the information from MBeans as described in the documentation. For example, i would like to see the responseCounts from the Router.

Connecting jconsole to service:jmx:rmi:///jndi/rmi://<ip address>:1100/apigee doesn't give me the information i want.

Am I missing something?

[#2]

@Wouter Leijdes what version of Edge are you using?

[#3]

we are using 4.16.05

[sgilson]

Sorry for the late reply, but the doc link you reference is for Edge 4.17.05. The link you want is: http://docs.apigee.com/private-cloud/v4.16.05/how-monitor which does not require those lines.

Were you able to make any progress?

Stephen

[sgilson]

one other comment: Isn't the JMX URL:

service:jmx:rmi:///jndi/rmi://<ip address>:<port>/platform

Stephen