I solved this event to the self. I thought that there was a problem in the version of jmx.jar of JBoss4.0.1sp1. Therefore, when exchanging for JBoss-jmx.jar offered with JBoss4.0.3sp1, and testing, the phenomenon was not generated.
It is everyone's favor. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3966348#3966348 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3966348 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
