You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Timothy Bish (JIRA)" <ji...@apache.org> on 2013/12/12 20:30:08 UTC
[jira] [Updated] (QPID-5419) [JMS Client] The JMS Client fails to
start a dispatcher thread for Durable Consumer's
[ https://issues.apache.org/jira/browse/QPID-5419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish updated QPID-5419:
-------------------------------
Attachment: DurableConsumerNoDispatcher.patch
Patch to fix this issue.
> [JMS Client] The JMS Client fails to start a dispatcher thread for Durable Consumer's
> -------------------------------------------------------------------------------------
>
> Key: QPID-5419
> URL: https://issues.apache.org/jira/browse/QPID-5419
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Affects Versions: 0.26
> Reporter: Timothy Bish
> Priority: Critical
> Fix For: 0.26
>
> Attachments: DurableConsumerNoDispatcher.patch
>
>
> When creating a MessageConsumer instance in the SessionImpl class the normal consumer case creates a Dispatcher instance via:
> {code}
> if(_dispatcherThread == null)
> {
> _dispatcherThread = new Thread(_dispatcher);
> _dispatcherThread.start();
> }
> {code}
> However in the create method for Durable Topic consumer's this is omitted causing any async MessageListener code to never receive any incoming Messages.
> This should really get into the 0.26 release as it breaks existing functionality in the 0.24 and lower versions.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org