[
http://jira.jboss.com/jira/browse/JBAS-3656?page=comments#action_12346240 ]
Brian Stansberry commented on JBAS-3656:
----------------------------------------
Let me have a look. Looking at the change history, seems I did this Sept 14, which tells
me it's in 4.0.5.GA (which makes sense -- I probably got it in when 4.0.5 was
delayed). When I closed it I probably missed removing the old 4.0.6.CR1 version.
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-5.0.0.Beta, JBossAS-4.0.5.GA, JBossAS-4.2.0.CR1,
JBossAS-4.0.5.SP1
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