[AMQNET-113] DispatchingThread.EventHandle is an AutoResetEvent potentially shared between threads

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Not A Problem
• Affects Version/s: 1.0.0
• Fix Version/s: 1.1.0
• Component/s: ActiveMQ
• Assignee: Jim Gomes
• Reporter: Chris Fraire
• Created: 08/Sep/08 16:02
• Updated: 07/Jan/11 03:26
• Resolved: 20/Feb/09 22:25

Description

Not sure it is an actual problem, but it seems suspect that a Session's DispatchingThread.EventHandle (AutoResetEvent) instance is associated with a MessageConsumer's Dispatcher when a Listener is attached. Since the EventHandle is an AutoResetEvent, it is possible that a DispatchingThread will miss a signal got instead by Dispatcher.Dequeue(Timespan). Is the correct behavior that they both be signaled?

Thanks,
Chris

Sub-Tasks

• Constructor for Apache.NMS.ActiveMQ.Connection invokes transport.Start(): Closed
• Threading issues -- Insufficient synchronization in Connection, Session, etc.: Closed