activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <>
Subject [jira] [Commented] (AMQ-3375) stomp consumer might not receive all msgs of a queue
Date Tue, 28 Jun 2011 22:39:28 GMT


Timothy Bish commented on AMQ-3375:

I can get the test to fail using the provided unit test however the problem appears to be
that the socket of the StompConnection is closed before the broker has had a chance to read
all the messages from the socket buffer, if you add a sleep (6 seconds on my machine) before
calling close the the test passes every time.

> stomp consumer might not receive all msgs of a queue
> ----------------------------------------------------
>                 Key: AMQ-3375
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.5.0
>         Environment: stomp consumer on virtual destination 
> Tested on Ubuntu 10.10 and MacOSX using java 6.
>            Reporter: Torsten Mielke
>              Labels: stomp, virtualTopic
>         Attachments: stomp-testcase.tgz
> Have a testcase that connects a Java stomp consumer to a virtual destination queue and
consumes a fixed amount of msgs.
> During the test I noticed that the consumer does not always receive the full amount of
> Instead the receive times out although JMX QueueSize property is greater than 0. However
when trying to browse the queue using JMX, it returns null, despite the fact that not all
msgs got dequeued yet (dispatch and dequeue counter < enqueue counter).
> So far I reproduced this with a stomp producer/consumer only. The producer writes msgs
to a virtual topic VirtualTopic.Foo and the consumer takes msgs off the Consumer.A.VirtualTopic.Foo
queue. Using JMX I noticed all msgs got moved from the virtual topic to the queue (reflected
by JMX enqueue counter) but not all msgs got consumed.
> So it seems the broker lost some msgs on the way. 

This message is automatically generated by JIRA.
For more information on JIRA, see:


View raw message