activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sree Panchajanyam D (JIRA)" <>
Subject [jira] [Commented] (AMQ-3460) Messages get stuck in the queue for some client sessions, "Dispatched Queue" grows but "Dequeues" doesn't move
Date Wed, 06 Nov 2013 17:09:18 GMT


Sree Panchajanyam D commented on AMQ-3460:

Reproducing the issue

This is reproducible but not with a Unit Test case. 
Steps to reproduce:
1. use the following broker url tcp://localhost:61616?randomize=false&timeout=60000  
// timeout is the most important part.
2. Use spring Default Message listener container for consuming messages.
3. Start the consumer application.
4. wait for 70 seconds and start ActiveMQ.
5. Consumers would be stuck - Issue would be reproduced
Note: This issue does not happen if ActiveMQ is started after 120 seconds. That is after the
second connection timeout. Issue can be reproduced with varying timeout values if AMQ is started
before the second timeout but after the first timeout. 

> Messages get stuck in the queue for some client sessions, "Dispatched Queue" grows but
"Dequeues" doesn't move
> --------------------------------------------------------------------------------------------------------------
>                 Key: AMQ-3460
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.3.1
>         Environment: java version "1.5.0_15"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_15-b04)
> Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_15-b04, mixed mode)
>            Reporter: Timur Evdokimov
>            Priority: Critical
>             Fix For: AGING_TO_DIE
>         Attachments: acmq01.png, acmq02.png
> We experience the following problem.
> There's 1 sender thread and 20 listener threads operating on the same queue.
> No other queues are involved.
> Message traffic goes generally OK via the queue, however Number of pending messages goes
up one by one.
> Looking at the active customers list, the following appears (see attached screenshot).
> For all sessions but two, the messages are dispatched properly.
> For these two affected sessions, the "Dispatched Queue" value gots stuck at certain moment
and doesn't deliver anymore.
> Eventually, more sessions got affected, and maybe after some hours, the stuck messages
got delivered.
> What we tried - adding useCache="false" into <policyEntry queue=">" ... > tag.
Didn't have any effect.

This message was sent by Atlassian JIRA

View raw message