activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "james strachan (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (AMQNET-30) Message dispatcher issues (use dedicated dispatching thread for each session)
Date Tue, 27 Feb 2007 12:27:03 GMT

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

james strachan resolved AMQNET-30.
----------------------------------

    Resolution: Fixed

> 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.


Mime
View raw message