Re: Not a NotificationBroadcaster...
"Simone Bordet" <[email protected]>
| Newsgroups | gmane.comp.java.mx4j.user |
|---|---|
| Message-ID | <[email protected]> |
Hi Chris, > Some background... > We are moving more to JDK1.5, we have a central JMX MBean repository > server - the rest of app runs in multiple JVMs each of which registers > their mbeans with the central server (via RMI/jsr 160). > > Admittedly we are still using MX4J 2.0.1 - I will try with 3.0.2 > shortly. My first thoughts are that some of the jsr 160 apis have > changed since 2.0.1 and so the upgrade will fix this. > > The problem we have noticed when the repository server is JDK1.5 and the > client is not, is that we sometimes get this error on the server: > > Nov-14 12:46:42.032 INFO : java.lang.IllegalArgumentException: MBean > YYY:process=XXX[kimptc],app=XXX,user=landar is not a > NotificationBroadcaster > at > mx4j.server.MX4JMBeanServer.addNotificationListener(MX4JMBeanServer.java > :525) Yes, I strongly recommend to move to MX4J 3.0.x. Maybe a dumb question, but the MBean does implement NotificationBroadcaster ? That exception only happens if it does not, or if there are ClassLoader problems. To run MX4J on JDK5 on the server, did you set the system property javax.management.builder.initial, and use MX4J's JSR 160 implementation via specifying a property in the environment Map of the JMXConnectorServer ? Simon -- http://bordet.blogspot.com ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV