You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Jim Gomes (JIRA)" <ji...@apache.org> on 2008/09/08 22:11:52 UTC
[jira] Updated: (AMQNET-113) DispatchingThread.EventHandle is an
AutoResetEvent potentially shared between threads
[ https://issues.apache.org/activemq/browse/AMQNET-113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jim Gomes updated AMQNET-113:
-----------------------------
Fix Version/s: 1.1
Affects Version/s: 1.0
> DispatchingThread.EventHandle is an AutoResetEvent potentially shared between threads
> -------------------------------------------------------------------------------------
>
> Key: AMQNET-113
> URL: https://issues.apache.org/activemq/browse/AMQNET-113
> Project: ActiveMQ .Net
> Issue Type: Bug
> Components: ActiveMQ Client
> Affects Versions: 1.0
> Reporter: Chris Fraire
> Assignee: James Strachan
> Priority: Minor
> Fix For: 1.1
>
>
> 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
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.