You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Rob Godfrey (JIRA)" <qp...@incubator.apache.org> on 2007/01/29 11:29:49 UTC
[jira] Created: (QPID-321) Simplify logic to deal with setting
MessageListener only after connection start has been called
Simplify logic to deal with setting MessageListener only after connection start has been called
-----------------------------------------------------------------------------------------------
Key: QPID-321
URL: https://issues.apache.org/jira/browse/QPID-321
Project: Qpid
Issue Type: Improvement
Components: Java Client
Reporter: Rob Godfrey
To deal with the case where the client program does not call .setMessageListener until after a connection has been started, we currently have a complicated piece of code which attempts to pause the Disptacher thread, and re-insert any messages which have already been delivered to the synchronous queue.
Instead, simply do not start the Dispatcher thread until either setMessageListener or receive() has been called.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (QPID-321) Simplify logic to deal with setting
MessageListener only after connection start has been called
Posted by "Robert Greig (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Greig resolved QPID-321.
-------------------------------
Resolution: Fixed
Fix Version/s: M2
Patch applied svn revision 501004
> Simplify logic to deal with setting MessageListener only after connection start has been called
> -----------------------------------------------------------------------------------------------
>
> Key: QPID-321
> URL: https://issues.apache.org/jira/browse/QPID-321
> Project: Qpid
> Issue Type: Improvement
> Components: Java Client
> Reporter: Rob Godfrey
> Fix For: M2
>
> Attachments: QPID-321.patch
>
>
> To deal with the case where the client program does not call .setMessageListener until after a connection has been started, we currently have a complicated piece of code which attempts to pause the Disptacher thread, and re-insert any messages which have already been delivered to the synchronous queue.
> Instead, simply do not start the Dispatcher thread until either setMessageListener or receive() has been called.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (QPID-321) Simplify logic to deal with setting
MessageListener only after connection start has been called
Posted by "Rob Godfrey (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rob Godfrey reassigned QPID-321:
--------------------------------
Assignee: Rob Godfrey
> Simplify logic to deal with setting MessageListener only after connection start has been called
> -----------------------------------------------------------------------------------------------
>
> Key: QPID-321
> URL: https://issues.apache.org/jira/browse/QPID-321
> Project: Qpid
> Issue Type: Improvement
> Components: Java Client
> Reporter: Rob Godfrey
> Assigned To: Rob Godfrey
> Fix For: M2
>
> Attachments: QPID-321.patch
>
>
> To deal with the case where the client program does not call .setMessageListener until after a connection has been started, we currently have a complicated piece of code which attempts to pause the Disptacher thread, and re-insert any messages which have already been delivered to the synchronous queue.
> Instead, simply do not start the Dispatcher thread until either setMessageListener or receive() has been called.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (QPID-321) Simplify logic to deal with setting
MessageListener only after connection start has been called
Posted by "Rob Godfrey (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rob Godfrey updated QPID-321:
-----------------------------
Attachment: QPID-321.patch
> Simplify logic to deal with setting MessageListener only after connection start has been called
> -----------------------------------------------------------------------------------------------
>
> Key: QPID-321
> URL: https://issues.apache.org/jira/browse/QPID-321
> Project: Qpid
> Issue Type: Improvement
> Components: Java Client
> Reporter: Rob Godfrey
> Attachments: QPID-321.patch
>
>
> To deal with the case where the client program does not call .setMessageListener until after a connection has been started, we currently have a complicated piece of code which attempts to pause the Disptacher thread, and re-insert any messages which have already been delivered to the synchronous queue.
> Instead, simply do not start the Dispatcher thread until either setMessageListener or receive() has been called.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.