Take the 2-minute tour ×  I've learned a lot about JMX over the
past couple of years and have built some pretty fancy MBeans for
my web applications. However, I'm not sure I have a good answer
to a pretty basic question:  Why use JMX over simple HTTP
servlets?  My current web applications offer redundant
monitoring options: I can access the data that needs to be
monitored via JMX with a client like JConsole or I can access
that same data in XML format via a servlet. I don't see a strong
reason to use one method over another, but the servlet method
does have the major advantage of being readable by a simple http
client / web browser.  I can see how JMX would be quite useful
for Java applications that aren't web apps, but I can't see any
advantage to using JMX for a web app.  share|improve this
question add comment  2 Answers  up vote 2 down vote accepted
Why use JMX over simple HTTP servlets?  From my standpoint, JMX
is better for 3 reasons:    1. It requires less code to enable
monitoring points.   2. It dea