[jboss-jira] [JBoss JIRA] Closed: (JBAS-5164) Generic ProxyFactoryHA leaves proxy in JNDI after undeploy
[ http://jira.jboss.com/jira/browse/JBAS-5164?page=all ]
Brian Stansberry closed JBAS-5164.
----------------------------------
Resolution: Done
Fixed by unregistering the DRM listener before destroying the target. The stopService()
method now does things in the exact opposite order that startService() does.
Generic ProxyFactoryHA leaves proxy in JNDI after undeploy
----------------------------------------------------------
Key: JBAS-5164
URL: http://jira.jboss.com/jira/browse/JBAS-5164
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Clustering
Affects Versions: JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Fix For: JBossAS-5.0.0.Beta4
An HA proxy created using org.jboss.proxy.generic.ProxyFactoryHA will get left in JNDI
following undeploy of the target service (and of the proxy factory itself).
This is because after the factory removes the proxy in stopService(), it remains as a
listener for DRM events. When it then destroys the HATarget, the target notifies the DRM,
which calls back into the proxy via it's listener. The listener rebinds the proxy
into JNDI.
--
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