aspose file tools
The moose likes Java in General and the fly likes JMX Requirements (JDK 5.0) Big Moose Saloon
  Search | Java FAQ | Recent Topics
Register / Login


Win a copy of Mongo DB Applied Patterns this week in the MongoDB forum
or a resume review from Five Year Itch in the Jobs Discussion forum!
JavaRanch » Java Forums » Java » Java in General
Reply 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
 
I agree. Here's the link: http://zeroturnaround.com/jrebel/download
 
subject: JMX Requirements (JDK 5.0)
 
Similar Threads
can be passivated when the bean instance is associated with a transaction?
examulator question error
doubt in beanName
really tricky question
Will I have two shopping carts?