It looks like this is a class loader problem. The MBean manages to read a .properties file from the fuse package but can't load classes from the same package. I can manufacture the same stack trace on first deploy of the MBean if I don't add the fuse package classes to the jar file. If I don't add the .properties file to the jar file then I get a different stack trace.
I'm guessing that the class loader isn't being configured properly when the MBean is deployed a second time.
I have configured log4j to log the class loader. Then I started jboss with my MBean deployed. Then I redeployed my MBean; this generates the error. Then I shutdown jboss.
The resulting log file can be found here:
Does this help?
This bug only occurs if I put the fuse package in my service/application. If I jar the fuse package seperately and put it in jboss/server/default/lib then the MBean works. The MBean continues to work after a redeploy too.
I'm guessing this is related to the class loading problems that the hibernate service people suffered?