[
https://jira.jboss.org/jira/browse/JBAS-4531?page=com.atlassian.jira.plug...
]
Brian Stansberry updated JBAS-4531:
-----------------------------------
Moving issues that won't happen for next AS release after 5.0.0 (whether called 5.0.1
or 5.1.0) to AS 6. It might get pulled back to a 5.x release; just don't want it on
the 5.0.1/5.10 roadmap which to me at this point both might mean "the one after
5.0.0.GA".
AsynchEventHandler should ignore queueEvent calls when stopped
--------------------------------------------------------------
Key: JBAS-4531
URL:
https://jira.jboss.org/jira/browse/JBAS-4531
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Clustering
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Priority: Minor
Fix For: JBossAS-6.0.0.Alpha1
AsynchEventHandler.queueEvent should not add events to its queue when it is stopped. If
an event is added after stop() is called, it can sit there for a long period and then be
handled if start() is called again. This could happen during a stop/start cycling of the
HAPartition.
This happens now with a MuxChannel that gets a viewAccepted as part of disconnecting --
ClusterPartition ends up putting an event in the stopped queue. That particular issue may
go away if JGroups decides to not issue the view, but we should be sure to handle such a
case properly.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira