I have tried the client on linux, with the same results. All of the messages are delivered - but they are out of order if the connection is broken. My application requires delivery in chronological order - and when the connection is intact all of the messages are delivered in order. When the connection is broken, and then reestablished, the messages are out of order.
Am I missing something in the broker configuration? Is there a way to reject the messages that are out of order? -- View this message in context: http://n2.nabble.com/0.5-C%2B%2B-example-listener-hangs-during-testing-tp3344401p3394145.html Sent from the Apache Qpid users mailing list archive at Nabble.com. --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:users-subscr...@qpid.apache.org
