Re: Not a NotificationBroadcaster...

Ok, thanks for the reply Simone. I forgot about that. At the time, I was
connecting to a Weblogic 8 JMX, which implements 1.0 spec. I found my post
from that issue:
http://archives.java.sun.com/cgi-bin/wa?A2=ind0608&L=jmx-forum&P=2992

Alper

-----Original Message-----
From: Simone Bordet [mailto:[email protected]]
Sent: Wednesday, November 15, 2006 7:19 AM
To: [email protected]
Subject: Re: [Mx4j-user] Not a NotificationBroadcaster...


Hi,

> I don't know if this is your problem (if not, you may run into this as
> well), but I had problems when client and server were not using the same
VM
> version, due to the different serial id of the ObjectName class. The only
> solution I could find was to run them both with the same version.

This is only true for JMX 1.0, which is very very old.
JMX 1.1 standardized the serial ids of all classes, and MX4J complies
with those, so the interoperability should not be a concern here.
If you have a detailed case that fails, I'll be interested.

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
_______________________________________________
Mx4j-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mx4j-user

-------------------------------------------------------------------------
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