So write a GaugeMonitorConfigurationService and the problem is solved. JMX is a non-remote spec as its base and has completely non-deterministic behavior when accessed over a remote connection since there are 0 guarentees with regard to remoteness at the jmx core. The jmx remoting spec does not address this basic issue.
Go join the jmx 2.0 spec and suggest that this be fixed. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3865320#3865320 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3865320 ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
