Changing the name of the service in the jboss-service.xml file was the solution to my problem. Though I don't know why that was the problem.
When I did the ObjectName lookup I tried both "com.relevant:service=E3Settings" and also "com.relevant:name=E3Settings" Thanks for the help, David View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3885700#3885700 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3885700 ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
