[
https://issues.apache.org/activemq/browse/AMQNET-30?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
james strachan moved AMQ-999 to AMQNET-30:
------------------------------------------
Fix Version/s: (was: 4.2.0)
1.0
Component/s: (was: NMS (C# client))
Affects Version/s: (was: 4.0.2)
Key: AMQNET-30 (was: AMQ-999)
Project: ActiveMQ .Net (was: ActiveMQ)
> Message dispatcher issues (use dedicated dispatching thread for each session)
> -----------------------------------------------------------------------------
>
> Key: AMQNET-30
> URL: https://issues.apache.org/activemq/browse/AMQNET-30
> Project: ActiveMQ .Net
> Issue Type: Improvement
> Environment: Windows
> Reporter: Rob Lugt
> Assigned To: james strachan
> Fix For: 1.0
>
> Attachments: amq999-patch.txt, AtomicBoolean.cs, DispatchingThread.cs
>
>
> There are a number of issues with the dispatching of inbound messages.
> - A slow consumer will potentially use and block all ThreadPool threads
> - Use of a ThreadPool thread to dispatch a single message is inefficient due
> to context switching
> - No mechanism to suspend asynchronous delivery to a session (i.e.
> Connection.Stop() is currently a no-op)
> - Retroactive consumer is currently broken because retoractive messages are
> delivered before the listener delegate is assigned.
> - [minor] Application cannot predict which thread messages will be dispatched
> on
> All of these problems can simply be resolved by creating a dedicated
> dispatcher thread for a session
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
