Effective October 27, 2012, online and email support for FuseSource products will move to Red Hat support channels. For more information, please see the JIRA Migration to Red Hat FAQ.
As of October 27th, please open all new issues in the Red Hat Customer Portal .
Issue Details (XML | Word | Printable)

Key: MB-1136
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Timothy Bish
Reporter: Jason Sherman
Votes: 0
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
FUSE Message Broker

PendingMessages not being dispatched to DurableSubscriber

Created: 11/Apr/12 07:00 PM   Updated: 01/Jun/12 01:31 PM
Component/s: broker
Affects Version/s: 5.5.1-fuse-03-06
Fix Version/s: 5.6.0-fuse-00-00, 5.5.1-fuse-07-11

File Attachments: 1. Zip Archive broker-test.zip (58 kB)
2. Java Source File DurableSubscriberNonPersistentMessageTest.java (12 kB)

Image Attachments:

1. DurableTopicSubscribers.jpg
(141 kB)

2. PendingMessage-ConsumerRestarted.jpg
(111 kB)

3. PendingMessage-TestComplete.jpg
(104 kB)
Environment:
5.5.1-fuse-03-06
5.4.2-fuse

External Issue URL: https://issues.apache.org/jira/browse/AMQ-3871


 Description  « Hide
Seems there might be an issue with DurableSubscribers and messages being dispatched to the consumer. It was reported that the PendingQueueSize shows message, however they dont appear to be dispatched to the consumer.

 All   Comments   Change History      Sort Order: Ascending order - Click to sort in descending order
Jason Sherman added a comment - 12/Apr/12 07:30 PM - edited
Attached test case.

This test shows that Non-Persistent messages are not being cleaned up on durable subscribers. The messages will not be delivered to the consumer, yet they remain and the broker stats for CursoryMemoryUsage and PendingQueueSize reflect these messages.

I have tested this against Apache ActiveMQ 5.5.1 and it does not have the same behavior and the attached test case passes.


Jason Sherman added a comment - 21/May/12 09:46 PM
Updated test case to work with Apache 5.6