[jboss-jira] [JBoss JIRA] Updated: (JBREM-166) JMXConnectorServer will not start if using rmi invoker elsewhere

JMXConnectorServer will not start if using rmi invoker elsewhere ---------------------------------------------------------------- Key: JBREM-166 URL: http://jira.jboss.com/jira/browse/JBREM-166 Project: JBoss Remoting Issue Type: Bug Components: jmx remoting Affects Versions: JMX Remoting 1.0.1 Reporter: Tom Elrod Fix For: JMX Remoting 1.0.2, 2.4.0.Beta1 (Pinto) If have a remoting invoker using rmi transport, it will create a rmi registry. Then when the JMXConnectorServer starts, it will also try to create one. Even though is on a different port, will get the following exception: java.rmi.server.ExportException: internal error: ObjID already in use at sun.rmi.transport.ObjectTable.putTarget(ObjectTable.java:168) at sun.rmi.transport.Transport.exportObject(Transport.java:69) at sun.rmi.transport.tcp.TCPTransport.exportObject(TCPTransport.java:190) at sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java:382) at sun.rmi.transport.LiveRef.exportObject(LiveRef.java:116) at sun.rmi.server.UnicastServerRef.exportObject(UnicastServerRef.java:145) at sun.rmi.registry.RegistryImpl.setup(RegistryImpl.java:92) at sun.rmi.registry.RegistryImpl.<init>(RegistryImpl.java:78) at java.rmi.registry.LocateRegistry.createRegistry(LocateRegistry.java:164) at org.jboss.mx.remoting.service.JMXConnectorServerService.start(JMXConnectorServerService.java:91)