[jboss-jira] [JBoss JIRA] Closed: (JBREM-82) Bad warning in Connector.

Bad warning in Connector. ------------------------- Key: JBREM-82 URL: http://jira.jboss.com/jira/browse/JBREM-82 Project: JBoss Remoting Issue Type: Bug Components: transport Affects Versions: 1.2.0 final Environment: In Jboss Head (CVS) Reporter: rimmeraj Assigned To: Tom Elrod Priority: Minor Fix For: 1.0.2 final JBoss head: remoting/src/main/org/jboss/remoting/transport/Connector.java , start method after you create the server invoker you try to register it with the mbean server. If it fails you register a warning. When you are using the ejb3 deployers it registers its own socket Connector. It is quite legal to have the standard Connector in conf/jboss-service.xml registers a socket protocol. The EJB3 deployer registers a socket listener on a different port. This triggers an annoying warning that in my option is more of a programming error that a valid warning. Warning. Error registering invoker org.jboss.remoting.transport.socket.SocketServerInvoker@51ef4e with MBeanServer. javax.management.InstanceAlreadyExistsException: jboss.remoting:service=invoker,transport=socket already registered. Suggested Fix. 1. org/jboss/remoting/transport/InvokerRegistry.java, createServerInvoker should log a warning if the InvokerLocator is already found. 2. Connector.java, start should check to see if the object name is not registered before trying. Something like ObjectName name=new ObjectName(invoker.getMBeanObjectName()); try { server.getInstance(name); } catch(InstanceNotFoundException e) { server.registerMBean(invoker, name); invoker.setMBeanServer(server); }