[jboss-jira] [JBoss JIRA] Closed: (JBCACHE-1025) JBossCache mbean registration fails on WebSphere 6.1

[Jerry Gauthier (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBCACHE-1025?page=all ]

Jerry Gauthier closed JBCACHE-1025.
-----------------------------------

    Resolution: Done

Verified problem on WebSphere.  It can be duplicated by deploying two independent cache applications which both use the default name (TreeCache-Group) for their cache name.  When the second cache application is started, registration of the cache's mbean will fail because the name is already registered.  Existing code in MBeanConfigurator to detect the prior registration fails because WebSphere registers the mbean under a different name (e.g., original name + WebSphere suffix).

Modified MBeanConfigurator so that it handles InstanceAlreadyExists exceptions.  When a registration attempt fails, MBeNConfigurator will issue a warning and processing will continue.

> JBossCache mbean registration fails on WebSphere 6.1
> ----------------------------------------------------
>
>                 Key: JBCACHE-1025
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1025
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.4.1.SP1, 1.4.1.SP2, 1.4.1.SP3
>         Environment: WebSphere 6.1
>            Reporter: Jerry Gauthier
>         Assigned To: Jerry Gauthier
>             Fix For: 1.4.1.SP4
>
>
> At least two customers have encountered the following problem when starting JBossCache on WebSphere 6.1.
> When the cache is started and the cache's interceptor mbeans are registered, the registration fails with an InstanceAlreadyExistsException. This occurs even on initial startup and despite the fact that JBossCache only registers a name if it's not already registered.
> A post to the ActiveMQ Forum at http://issues.apache.org/activemq/browse/SM-883 suggest that this problem occurs because WebSphere modifies the mbean's registration name during the registration process.  Subsequent tests to determine if the mbean has been registered apparently fail unless the client uses the name generated by WebSphere.  (This is unverified but seems plausible.)
> Caused by: javax.management.InstanceAlreadyExistsException:jboss.cache:service=TreeCache-Group,cell=citgoNode01Cell,nod
> e=citgoNode01,process=server1
> at com.sun.jmx.mbeanserver.RepositorySupport.addMBean(RepositorySupport.java:452)
> at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.internal_addObject(DefaultMBeanServerInterceptor.java:1410)
> at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:936)
> at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:337)
> at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:497)
> at com.ibm.ws.management.PlatformMBeanServer.registerMBean(PlatformMBeanServer.java:469)
> at org.jboss.cache.util.MBeanConfigurator.registerInterceptors(MBeanConfigurator.java:72)
> at org.jboss.cache.TreeCache._createService(TreeCache.java:1428)
> at org.jboss.cache.TreeCache.createService(TreeCache.java:1378)
> at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:260)
> at org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:188)

-- 
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