[rabbitmq-discuss] Fwd: STOMP adapter lose the last message of a burst

[Steve Powell]

Sent to google-groups by mistake.
Steve Powell
steve at rabbitmq.com
[wrk: +44-2380-111-528] [mob: +44-7815-838-558]

Begin forwarded message:

> From: Steve Powell <steve at rabbitmq.com>
> Date: 18 May 2012 11:22:37 GMT+01:00
> To: José Micó <jose.mico at gmail.com>
> Cc: rabbitmq-discuss at googlegroups.com
> Subject: Re: [rabbitmq-discuss] STOMP adapter lose the last message of a burst
> 
> Hi José,
> 
> This may very well be a bug, but could also be something about flushing
> in the Perl script you are using.
> 
> Please can you tell us which version of RabbitMQ and STOMP you are
> using?
> 
> Steve Powell
> steve at rabbitmq.com
> [wrk: +44-2380-111-528] [mob: +44-7815-838-558]
> 
> On 18 May 2012, at 06:18, José Micó wrote:
> 
>> I think I've found a somewhat serious bug in the STOMP adapter: after a burst of incoming messages, the last one remains buffered somewhere indefinitely and is not added to the queue until another message is received from the same connection (same with topics). This cause and excessive delay to deliver the message to consumers, if it is ever delivered. Besides that, that last message is lost if the connection is not properly closed.
>> 
>> I've attached a simple script which replicates the bug. It sends burst of 100 small messages to a queue every 10 seconds. Using the management console, we can inspect the count of Ready messages. The expected progression is 100 ... 200 ... 300 ... 400 ... 500, but very frequently (not always) we get 99 ... 199 ... 299 ... 399 ... 499, as the last message is not queued.
>> 
>> Could be that the STOMP parser gets confused after an incomplete frame was read from tcp buffer? Any ideas?
>> 
>> Regards,
>> José
>> <stomp_bug.pl>_______________________________________________
>> rabbitmq-discuss mailing list
>> rabbitmq-discuss at lists.rabbitmq.com
>> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20120518/10f0ce43/attachment.htm>