[
https://issues.apache.org/jira/browse/QPID-577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell closed QPID-577.
-------------------------------
Resolution: Won't Fix
Closing thess issues out as they relate to the old 0-8 and 0-10 .Net clients
which were removed from the repository months ago, and not the current .Net
bindings for the C++ messaging API.
> Setting a MessageListener after the connection has been started may result in
> apparent message loss.
> ----------------------------------------------------------------------------------------------------
>
> Key: QPID-577
> URL: https://issues.apache.org/jira/browse/QPID-577
> Project: Qpid
> Issue Type: Bug
> Components: Dot Net Client
> Affects Versions: M1, M2, M3
> Reporter: Martin Ritchie
>
> When the connection is started and messages are received the are placed on
> the _synchronousQueue awaiting a receive() call. If the message listener is
> subsquently set the messages in this queue is not delivered, only new messges.
> There are two options available.
> 1) reject all the _sQueue messages causing them to be redelivered.
> 2) ensure the ordering is preserved and push the messages through the message
> listener.
> To verify this is the case create the following test:
> Create consumer.
> start consumer
> publish messages to the consumer
> read first message.
> (rest of messages will now be in _syncQueue)
> attach messages listener
> (no messages will appear !BUG!)
> send final message
> message listener will receive message.
> close consumer
> and reopen
> (there should be no messages, but all the messages between first and last
> will be recevied)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
