Oops.. lets make that rmi not rim...
Damn finger trouble :-)
update to latest versions that implement jmx 1.1 serialization
That kind of sucks actually.
I've been working on a revised version of the JMX Console Web App....one that uses the JBoss RMI JMX interface (ie. using RemoteMBeanServer), instead of using the in-process MBeanServer instance, so that I can run the JMX Console in an external Tomcat container (ie. one running in a different JVM than JBoss...not embedded).
And since Tomcat 4.1.12 and JBoss 3.0.4 use different versions of the javax.management.ObjectName class, the JMX Console servlet code picks up the Tomcat version and thus cannot talk to JBoss JMX properly due to the serialization mismatch.
Which version of JBoss is using JMX 1.1 (or whatever is compatible with Tomcat 4.1.12)?
1.1 serialization compliance is included in the 3.2 branch, dropping MX 1.1.1 jar into 3.0.x will probably work too (though I haven't tried)
Is there somewhere I can find the pre-built JMX 1.1.1 jars?
Or do I have to build 'em from source?
3.2beta2 will be out soon (this week?)
Copy jboss-jmx.jar from there.
Sorry, I would backport the jmx serialization to 3.0
but it would have stopped 3.0.4 "talking jmx" to previous
versions of 3.0
The real problem was the jmx 1.0 spec not including
a class serialization section.
Incidently, I think jdmk uses the same code as the RI.
There are some serious problems with their modelmbean
code if you enable "1.0" compatibilty, especially on
a 1.3 VM - "1.1" serialization is the default
If you intend to use QueryExp, it won't work.
This still isn't specified by the 1.1 spec. :-(