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.
