[jboss-jira] [JBoss JIRA] Closed: (JBAS-3656) Disconnect HAPartition channel upon failure in startService()
Brian Stansberry (JIRA)
jira-events at jboss.com
Mon Nov 13 10:56:41 EST 2006
[ http://jira.jboss.com/jira/browse/JBAS-3656?page=all ]
Brian Stansberry closed JBAS-3656.
----------------------------------
Fix Version/s: (was: JBossAS-5.0.0.Beta1)
(was: JBossAS-4.2.0.CR1)
(was: JBossAS-4.0.5.SP1 )
Resolution: Done
Confirmed this was fixed for 4.0.5.GA.
> Disconnect HAPartition channel upon failure in startService()
> -------------------------------------------------------------
>
> Key: JBAS-3656
> URL: http://jira.jboss.com/jira/browse/JBAS-3656
> Project: JBoss Application Server
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Clustering
> Reporter: Brian Stansberry
> Assigned To: Brian Stansberry
> Priority: Critical
> Fix For: JBossAS-4.0.5.GA
>
>
> If an exception is thrown in ClusterPartition/HAPartition startService() after the channel is connected, the channel must be disconnected, or we've left a zombie member of the group. Particularly in 4.0.x where the ServiceController will not undeploy a service that fails in start().
> Need to ensure stopService() properly handles a disconnected channel.
--
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
More information about the jboss-jira
mailing list