Knowledge Drop

JMX monitoring when using --no-daemonise flag

  • 7 July 2021
  • 0 replies
  • 38 views

Userlevel 3
Badge

Last tested: Oct 5, 2017
 

You will need to change all of the JMX-related startup flags by removing com.sun.akuma.jvmarg.
like this:

-Dcom.sun.management.jmxremote \

-Dcom.sun.management.jmxremote.port=9910 \

-Dcom.sun.management.jmxremote.ssl=false \

-Dcom.sun.management.jmxremote.local.only=false \

-Dcom.sun.management.jmxremote.authenticate=true \

-Dcom.sun.management.jmxremote.access.file=${HOME}/.lookerjmx/jmxremote.access \

-Dcom.sun.management.jmxremote.password.file=${HOME}/.lookerjmx/jmxremote.password \

 

These were a workaround to keep the daemonizer from grabbing the JMX ports, which kept the child process from starting.

 

This content is subject to limited support.                

 

 


0 replies

Be the first to reply!

Reply