activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jim Gomes (JIRA)" <jira+amq...@apache.org>
Subject [jira] Resolved: (AMQNET-113) DispatchingThread.EventHandle is an AutoResetEvent potentially shared between threads
Date Fri, 20 Feb 2009 22:26:59 GMT

     [ https://issues.apache.org/activemq/browse/AMQNET-113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jim Gomes resolved AMQNET-113.
------------------------------

    Resolution: Working as Designed
      Assignee: Jim Gomes  (was: James Strachan)

It is my understanding that AutoResetEvents will signal any and all listeners, so one listener
can't "steal" the event away from another.  If there is a specific problem that can be identified
with this code, please re-open or enter a new JIRA for that.  Otherwise, I can't identify
a specific issue here.

> 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: Jim Gomes
>            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.


Mime
View raw message