activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Timothy Bish <tabish...@gmail.com>
Subject Re: Stomp 1.1 - first message sent to broker after heart-beat time-out is "lost"
Date Sat, 19 Nov 2011 17:21:41 GMT
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.
> 
> However the client can successfully send one message to the broker.
> 
> Because the client does not see an error, he assumes that the message is 
> transmitted successfully.
> 
> The next (second) message sent will be rejected by the broker.
> 
> Maybe this test case could be added to the Stomp11Tests code?
> 
> 
> send:
> CONNECT
> accept-version:1.1
> server:localhost
> heart-beat:1000,0
> 
> 
> 
> received:
> CONNECTED
> heart-beat:0,2000
> session:ID:mj-PC-49595-1314256305896-2:24
> server:ActiveMQ/5.6-SNAPSHOT
> version:1.1
> 
> 
> -- wait for five seconds --
> 
> send:
> SEND
> destination:/queue/TOOL.DEFAULT

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 was closed as inactive.



> 
> 
> 
> send:
> DISCONNECT
> 
> Thanks and regards



Mime
View raw message