Accessing mbeans remotely (r/w attributes, invoke operations) will not be a problem, as long as the exhanged data is serializalbe (which is normal).
The problem you see is when asking for the MBeanInfo of mbeans. JBoss internally uses ModelMBeanInfo (an extension of MBeanInfo) that contains extra metadata and also javax.management.Descriptor objects containing runtime data (e.g. cached attribute values). If an attribute is of a non-serializable type and it has been set, the Descriptor will have it's cached value. I presume those non-serializable field should not be carried over, so (a) try first using jdk5 on both sides to pick up the sun implementation of Descriptor so we see if this is a jboss jmx implementation bug (b) open a bug report in JIRA. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3918044#3918044 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3918044 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
