That's what the code in ServiceContainer.startRemoting does currently - deploys a RemotingJMXWrapper using the same ObjectName that a Connector would normally be deployed under. RemotingJMXWrapper emulates the Connector but also keeps track of some additional info that Connector doesn't provide. Here is its Javadoc: * Note: This wrapper MUST NOT allow direct access to the Connector instance. This is necessary | * because the wrapper is maintaining the mapping between the Connector's | * ServerInvocationHandler instances and their subsystem names. Remoting should do that (it | * should have a Connector.getSubsystemNames() or similar), but it doesn't, so I have to do | * this by myself. | * | * @author <a href="mailto:ovidiu@jboss.org">Ovidiu Feodorov</a> View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4053398#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...