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 Fri, 12 Jul 2013 10:51:50 GMT


Sree Panchajanyam D commented on AMQ-3460:

I am facing the same issue in 5.6.0 as well. The most frustrating part is that it is not reproducible.
Restart of consumers solves this issue. Does anybody here have Debug logs during the issue?
Or steps to reproduce this issue?

> 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
>         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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message