Link ServerInvokerServlet instances to Connectors via MBean names rather than locator URLs ------------------------------------------------------------------------------------------ Key: JBREM-1100 URL: https://jira.jboss.org/jira/browse/JBREM-1100 Project: JBoss Remoting Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 2.2.2.SP10 Reporter: Galder Zamarreno Fix For: 2.2.2.SP12 Following instructions in http://www.jboss.org/community/docs/DOC-9632, you get the following warning messages when AS/EAP starts up: 11:41:29,289 WARN [Connector] jboss.remoting:service=invoker,transport=servlet is already registered with MBeanServer 11:41:29,290 WARN [Connector] jboss.remoting:service=invoker,transport=servlet is already registered with MBeanServer 11:41:29,291 WARN [Connector] jboss.remoting:service=invoker,transport=servlet is already registered with MBeanServer 11:41:29,292 WARN [Connector] jboss.remoting:service=invoker,transport=servlet is already registered with MBeanServer 11:41:29,293 WARN [Connector] jboss.remoting:service=invoker,transport=servlet is already registered with MBeanServer They come from the other servlet invokers trying to register the default invoker name in the MBeanServer. A better solution, and a way to avoid these WARN messages, would be for invokerName to work properly and point to the corresponding connectors rather than using locatorUrl which are prone to error. This was not possible when I started working on the unified http invokers. Ron/David, I think we might have discussed using MBean names rather than locator URLs in the past but can't find the email. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira