[jira] [Updated] (AMQ-3375) stomp consumer might not receive all msgs of a virtual topic queue with memory limits

["Gary Tully (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/AMQ-3375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Tully updated AMQ-3375:
----------------------------

    Assignee: Gary Tully
     Summary: stomp consumer might not receive all msgs of a virtual topic queue with memory limits  (was: stomp consumer might not receive all msgs of a queue)

> stomp consumer might not receive all msgs of a virtual topic queue with memory limits
> -------------------------------------------------------------------------------------
>
>                 Key: AMQ-3375
>                 URL: https://issues.apache.org/jira/browse/AMQ-3375
>             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
>            Assignee: Gary Tully
>              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 msgs.
> 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: http://www.atlassian.com/software/jira