Wednesday, 15 June 2011

java - JMX not available for spring boot application when running standalone -


I do need to keep an eye on a spring boot application and using Jemaks application with an embedded Jetti.

I can use jconsole with jmx information unless I start application in your Windows development environment (Jesinsol provides process of joining myself) do, but as long as the run down to run an application as an executable jar with the parameters of ports that are available and I can not connect to Jeconsol

  -Dcom.sun.management.jmxremote -Dcom.sun .management.jmxremote.port = 9010 -Dcom.sun.management.jmxremote.ssl = F alse -Dcom.sun.management.jmxremote.authenticate = false -Dcom.sun.management.jmxremote.local.only = false -Dajava.rmi.server.hostname = [server ip] -Djava.rmi.activation.port = 9011  

netstat -tulpn neither returns port 9010 nor port 9011, and I can not connect via jconsole.

MBNs are available because I know JMX information using JSON, Jolikai, which is working fine but is not fit in our monitoring infrastructure.

Try the following criteria.

  set JMX_OPTIONS = -Dcom.sun.management.jmxremote.port = 8014 set JMX_OPTIONS =% JMX_OPTIONS% -Dcom.sun.management.jmxremote.ssl = false set JMX_OPTIONS =% JMX_OPTIONS% - Dcom.sun Management.jmxremote.authenticate = false set JMX_OPTIONS =% JMX_OPTIONS% -Dcom.sun.management.jmxremote.localConnectorAddress = 10.250.0.10  

No comments:

Post a Comment