Re: Stomp 1.1 - first message sent to broker after heart-beat time-out is "lost"

2011-11-22 Thread Michael Justin
Am 21.11.2011 08:56, Michael Justin wrote: Am 19.11.2011 18:21, Timothy Bish wrote: If you want to be sure that the message is processed, then you need to add a receipt request, otherwise the delivery is not guaranteed. You await the receipt an once received you know the broker had a chance to

Re: Stomp 1.1 - first message sent to broker after heart-beat time-out is "lost"

2011-11-20 Thread Michael Justin
Am 19.11.2011 18:21, Timothy Bish wrote: If you want to be sure that the message is processed, then you need to add a receipt request, otherwise the delivery is not guaranteed. You await the receipt an once received you know the broker had a chance to process the message before the connection

Re: Stomp 1.1 - first message sent to broker after heart-beat time-out is "lost"

2011-11-19 Thread Timothy Bish
On Sat, 2011-11-19 at 16:40 +0100, Michael Justin wrote: > Hello, > > For the current 5.6 snapshot, I wrote a test which sends a frame after > the time-out of the heart-beat elapsed. > > Expected behaviour is that the broker does not accept any more data from > the socket connection. > > Howev

Stomp 1.1 - first message sent to broker after heart-beat time-out is "lost"

2011-11-19 Thread Michael Justin
Hello, For the current 5.6 snapshot, I wrote a test which sends a frame after the time-out of the heart-beat elapsed. Expected behaviour is that the broker does not accept any more data from the socket connection. However the client can successfully send one message to the broker. Because