This week's book giveaway is in the Mac OS forum.
We're giving away four copies of a choice of "Take Control of Upgrading to Yosemite" or "Take Control of Automating Your Mac" and have Joe Kissell on-line!
See this thread for details.
The moose likes Java in General and the fly likes JMX Requirements (JDK 5.0) Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


JavaRanch » Java Forums » Java » Java in General
Bookmark "JMX Requirements (JDK 5.0)" Watch "JMX Requirements (JDK 5.0)" New topic
Author

JMX Requirements (JDK 5.0)

jeff kearns
Greenhorn

Joined: Aug 01, 2006
Posts: 1
I am confused as to what exactly is required in order to be able to view and monitor your beans through a program such as JConsole. I tried just placing the following in my Tomcat arguement's, and could connect, but no beans were displayed:

-Dcom.sun.management.jmxremote
-Dcom.sun.management.jmxremote.port=12875
-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.ssl=false

Thanks
Amit K Srivastava
Greenhorn

Joined: May 16, 2006
Posts: 23
I am assuming that your MBean complies the specifications. Check the following-
1. Is the MBean to be monitored is registered with the MBean server? If not create an Agent which will register it with the MBean server (its not a separate server you need to install JDK can be used there).
2. Once registered and the MBean Server is up, you can get the MBean instance from the Server and invoke the various management APIs you have written in your MBean.

--AmitS
 
GeeCON Prague 2014
 
subject: JMX Requirements (JDK 5.0)