Connector.stop() cannot find invoker MBean when bind address is 0.0.0.0 ----------------------------------------------------------------------- Key: JBREM-909 URL: http://jira.jboss.com/jira/browse/JBREM-909 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Ron Sigal Assigned To: Ron Sigal Priority: Minor Fix For: 2.4.0.CR1 (Pinto) org.jboss.remoting.transport.Connector.init() registers its org.jboss.remoting.ServerInvoker with the MBeanServer using the ObjectName returned by ServerInvoker.getMBeanObjectName(), and Connector.stop() unregisters the same ServerInvoker using the ObjectName returned by ServerInvoker.getMBeanObjectName(). The problem is that Connector.init() calls ServerInvoker.getMBeanObjectName() before it calls ServerInvoker.create(), at which time ServerInvoker transforms the original 0.0.0.0 bind address into an actual address. Since the bind address is used in the ObjectName, the opening and closing calls to ServerInvoker.getMBeanObjectName() return different values when the original bind address is 0.0.0.0. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira