learning_java_jmx_jmxmp.md

path	title
/learnings/ops_java_jmx_jmxmp	Learnings: Ops: Java: JMX: JMXMP

Table Of Contents

• >
  • Background:
• JMX Over HTTP >
• JMX And GC Debugging >
  • Why not
• >

<<Learinng_Ops_Java_JMX>>

Start here: Platform Monitoring and Management with JMX

Background:

Traditional JMX / RMI works the following way:

1. Client request goes into JMX port
2. Server responds with port in RMI range
3. Client connects on that port

See also:

• Learning_Ops_Java_Docker_JMX_Considerations

JMX Over HTTP <<Learning_Ops_Java_JMX_HTTP_Solution_Jolokia>>

Use Jolokia. Allows read, write, exec of attributes, beans

See also:

• https://www.ctheu.com/2017/02/14/all-the-things-we-can-do-with-jmx/#jolokia-jmx-to-http

JMX And GC Debugging <<Learning_Ops_Java_JMX_GC_Debugging>>

Why not

• JMX usually uses sampling runtime, thus can not know when collector ran thus unknown state of before / after memory

• Optimizing Java 8.1

<<Learning_Java_JMX_Useful_mbeans>>

• thread information (ThreadMXBean)