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.