• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Tim Cooke
  • paul wheaton
  • Jeanne Boyarsky
  • Ron McLeod
Sheriffs:
  • Paul Clapham
  • Liutauras Vilda
  • Devaka Cooray
Saloon Keepers:
  • Tim Holloway
  • Roland Mueller
Bartenders:

JMX Requirements (JDK 5.0)

 
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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
 
Greenhorn
Posts: 23
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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
 
Willie Smits can speak 40 languages. This tiny ad can speak only one:
Smokeless wood heat with a rocket mass heater
https://woodheat.net
reply
    Bookmark Topic Watch Topic
  • New Topic