You are viewing a plain text version of this content. The canonical link for it is here.
Posted to savan-dev@ws.apache.org by "Hiranya Jayathilaka (JIRA)" <ji...@apache.org> on 2010/07/21 06:35:50 UTC
[jira] Created: (AXIS2-4784) Transport MBean Registration Error at
Startup
Transport MBean Registration Error at Startup
---------------------------------------------
Key: AXIS2-4784
URL: https://issues.apache.org/jira/browse/AXIS2-4784
Project: Axis2
Issue Type: Bug
Components: transports
Affects Versions: nightly
Reporter: Hiranya Jayathilaka
Fix For: 1.6
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.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Resolved: (AXIS2-4784) Transport MBean Registration Error at
Startup
Posted by "Afkham Azeez (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Afkham Azeez resolved AXIS2-4784.
---------------------------------
Assignee: Afkham Azeez
Resolution: Fixed
Applied patch
> Transport MBean Registration Error at Startup
> ---------------------------------------------
>
> Key: AXIS2-4784
> URL: https://issues.apache.org/jira/browse/AXIS2-4784
> Project: Axis2
> Issue Type: Bug
> Components: transports
> Affects Versions: nightly
> Reporter: Hiranya Jayathilaka
> Assignee: Afkham Azeez
> Fix For: 1.6
>
> 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.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Updated: (AXIS2-4784) Transport MBean Registration Error at
Startup
Posted by "Hiranya Jayathilaka (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hiranya Jayathilaka updated AXIS2-4784:
---------------------------------------
Attachment: AXIS2-4784.patch
Here's a quick fix for the problem at hand. It appends the object hashcode to the MBean name to make it unique. Since the hashcode values are generally short in length, names do not become ridiculously longer as in the case of appending a UUID.
> Transport MBean Registration Error at Startup
> ---------------------------------------------
>
> Key: AXIS2-4784
> URL: https://issues.apache.org/jira/browse/AXIS2-4784
> Project: Axis2
> Issue Type: Bug
> Components: transports
> Affects Versions: nightly
> Reporter: Hiranya Jayathilaka
> Fix For: 1.6
>
> 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.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Updated: (AXIS2-4784) Transport MBean Registration Error at
Startup
Posted by "Hiranya Jayathilaka (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hiranya Jayathilaka updated AXIS2-4784:
---------------------------------------
Attachment: AXIS2-4784.patch
Here's a quick fix for the problem at hand. It appends the object hashcode to the MBean name to make it unique. Since the hashcode values are generally short in length, names do not become ridiculously longer as in the case of appending a UUID.
> Transport MBean Registration Error at Startup
> ---------------------------------------------
>
> Key: AXIS2-4784
> URL: https://issues.apache.org/jira/browse/AXIS2-4784
> Project: Axis2
> Issue Type: Bug
> Components: transports
> Affects Versions: nightly
> Reporter: Hiranya Jayathilaka
> Fix For: 1.6
>
> 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.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Resolved: (AXIS2-4784) Transport MBean Registration Error at
Startup
Posted by "Afkham Azeez (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Afkham Azeez resolved AXIS2-4784.
---------------------------------
Assignee: Afkham Azeez
Resolution: Fixed
Applied patch
> Transport MBean Registration Error at Startup
> ---------------------------------------------
>
> Key: AXIS2-4784
> URL: https://issues.apache.org/jira/browse/AXIS2-4784
> Project: Axis2
> Issue Type: Bug
> Components: transports
> Affects Versions: nightly
> Reporter: Hiranya Jayathilaka
> Assignee: Afkham Azeez
> Fix For: 1.6
>
> 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.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Resolved: (AXIS2-4784) Transport MBean Registration Error at
Startup
Posted by "Afkham Azeez (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Afkham Azeez resolved AXIS2-4784.
---------------------------------
Assignee: Afkham Azeez
Resolution: Fixed
Applied patch
> Transport MBean Registration Error at Startup
> ---------------------------------------------
>
> Key: AXIS2-4784
> URL: https://issues.apache.org/jira/browse/AXIS2-4784
> Project: Axis2
> Issue Type: Bug
> Components: transports
> Affects Versions: nightly
> Reporter: Hiranya Jayathilaka
> Assignee: Afkham Azeez
> Fix For: 1.6
>
> 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.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Resolved: (AXIS2-4784) Transport MBean Registration Error at
Startup
Posted by "Afkham Azeez (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Afkham Azeez resolved AXIS2-4784.
---------------------------------
Assignee: Afkham Azeez
Resolution: Fixed
Applied patch
> Transport MBean Registration Error at Startup
> ---------------------------------------------
>
> Key: AXIS2-4784
> URL: https://issues.apache.org/jira/browse/AXIS2-4784
> Project: Axis2
> Issue Type: Bug
> Components: transports
> Affects Versions: nightly
> Reporter: Hiranya Jayathilaka
> Assignee: Afkham Azeez
> Fix For: 1.6
>
> 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.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Updated: (AXIS2-4784) Transport MBean Registration Error at
Startup
Posted by "Hiranya Jayathilaka (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hiranya Jayathilaka updated AXIS2-4784:
---------------------------------------
Attachment: AXIS2-4784.patch
Here's a quick fix for the problem at hand. It appends the object hashcode to the MBean name to make it unique. Since the hashcode values are generally short in length, names do not become ridiculously longer as in the case of appending a UUID.
> Transport MBean Registration Error at Startup
> ---------------------------------------------
>
> Key: AXIS2-4784
> URL: https://issues.apache.org/jira/browse/AXIS2-4784
> Project: Axis2
> Issue Type: Bug
> Components: transports
> Affects Versions: nightly
> Reporter: Hiranya Jayathilaka
> Fix For: 1.6
>
> 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.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Updated: (AXIS2-4784) Transport MBean Registration Error at
Startup
Posted by "Hiranya Jayathilaka (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hiranya Jayathilaka updated AXIS2-4784:
---------------------------------------
Attachment: AXIS2-4784.patch
Here's a quick fix for the problem at hand. It appends the object hashcode to the MBean name to make it unique. Since the hashcode values are generally short in length, names do not become ridiculously longer as in the case of appending a UUID.
> Transport MBean Registration Error at Startup
> ---------------------------------------------
>
> Key: AXIS2-4784
> URL: https://issues.apache.org/jira/browse/AXIS2-4784
> Project: Axis2
> Issue Type: Bug
> Components: transports
> Affects Versions: nightly
> Reporter: Hiranya Jayathilaka
> Fix For: 1.6
>
> 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.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Updated: (AXIS2-4784) Transport MBean Registration Error at
Startup
Posted by "Hiranya Jayathilaka (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hiranya Jayathilaka updated AXIS2-4784:
---------------------------------------
Attachment: AXIS2-4784.patch
Here's a quick fix for the problem at hand. It appends the object hashcode to the MBean name to make it unique. Since the hashcode values are generally short in length, names do not become ridiculously longer as in the case of appending a UUID.
> Transport MBean Registration Error at Startup
> ---------------------------------------------
>
> Key: AXIS2-4784
> URL: https://issues.apache.org/jira/browse/AXIS2-4784
> Project: Axis2
> Issue Type: Bug
> Components: transports
> Affects Versions: nightly
> Reporter: Hiranya Jayathilaka
> Fix For: 1.6
>
> 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.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Resolved: (AXIS2-4784) Transport MBean Registration Error at
Startup
Posted by "Afkham Azeez (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Afkham Azeez resolved AXIS2-4784.
---------------------------------
Assignee: Afkham Azeez
Resolution: Fixed
Applied patch
> Transport MBean Registration Error at Startup
> ---------------------------------------------
>
> Key: AXIS2-4784
> URL: https://issues.apache.org/jira/browse/AXIS2-4784
> Project: Axis2
> Issue Type: Bug
> Components: transports
> Affects Versions: nightly
> Reporter: Hiranya Jayathilaka
> Assignee: Afkham Azeez
> Fix For: 1.6
>
> 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.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org