axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andreas Veithen (JIRA)" <j...@apache.org>
Subject [jira] [Moved] (TRANSPORTS-37) Transport MBean Registration Error at Startup
Date Sat, 18 Jun 2011 11:39:48 GMT

     [ https://issues.apache.org/jira/browse/TRANSPORTS-37?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Andreas Veithen moved AXIS2-4784 to TRANSPORTS-37:
--------------------------------------------------

        Fix Version/s:     (was: 1.6.0)
                       1.6.0
          Component/s:     (was: transports)
                       Base
    Affects Version/s:     (was: nightly)
                       1.0.0
                  Key: TRANSPORTS-37  (was: AXIS2-4784)
              Project: Axis2 Transports  (was: Axis2)

> Transport MBean Registration Error at Startup
> ---------------------------------------------
>
>                 Key: TRANSPORTS-37
>                 URL: https://issues.apache.org/jira/browse/TRANSPORTS-37
>             Project: Axis2 Transports
>          Issue Type: Bug
>          Components: Base
>    Affects Versions: 1.0.0
>            Reporter: Hiranya Jayathilaka
>            Assignee: Afkham Azeez
>             Fix For: 1.6.0
>
>         Attachments: AXIS2-4784.patch
>
>
> 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.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org


Mime
View raw message