I have added some reconnect logic to the example listener that I am running on windows, and now when the connection is broken the listener reconnects and I can continue receiving messages. At this point I have not detected any missing messages. I have received one duplicate message, but I believe that is to be expected when I break the ethernet connection in the middle of transmission.
I also noticed that all the messages are delivered, however some are delivered out of order. I have been testing with serialized messages, when the connection remains constant - i get messages 1-10 in order. But, if the connection is broken (lets say at message 3) - when I restore the connection some time later - I do not get 4, I get a message that was created later (say 8 for example). The message delivery order becomes scrambled - lets say 1,2,3,8,9,4,5,6,7,10. Is there a way to get the messages to be delivered in order? -- View this message in context: http://n2.nabble.com/0.5-C%2B%2B-example-listener-hangs-during-testing-tp3344401p3356545.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
