[AXIS2-5556] Transport MBean Registration Error at Startup

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Transports 1.0.0
• Fix Version/s: 1.6.3, 1.7.0
• Component/s: transports
• Assignee: Afkham Azeez
• Reporter: Hiranya Kasub Jayathilaka
• Created: 21/Jul/10 04:35
• Updated: 10/May/13 11:07
• Resolved: 21/Jul/10 05:57

Description

When initializing multiple configuration context instances in the same application (say client cfgCtx and server cfgCtx) the following exception might be thrown if the same transport listener or sender is configured in multiple axis2.xml files:

[2010-07-20 17:19:59,815] WARN

{org.apache.axis2.transport.base.TransportMBeanSupport}

- Error registering a MBean with objectname ' org.apache.axis2:Type=Transport,ConnectorName=tcp-sender ' for JMX management
javax.management.InstanceAlreadyExistsException: org.apache.axis2:Type=Transport,ConnectorName=tcp-sender
at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:453)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.internal_addObject(DefaultMBeanServerInterceptor.java:1484)

This is because when we take a particular transport listener or a sender they use the same name to register their JMX MBeans. Transports should use more unique names when registering their MBeans.