activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "William (Commented) (JIRA)" <>
Subject [jira] [Commented] (AMQ-3697) Messages not delivered to connecter consumer
Date Sun, 05 Feb 2012 16:19:53 GMT


William commented on AMQ-3697:

Ok but does 5.6.0 is suitable for production ?

I have patched my 5.5.1 version with AMQ-3454 for performance reasons. Does this fix is included
in FuseSource 5.5.1 ?

And alseo what is the difference between ActiveMQ and FuseSource ?

> Messages not delivered to connecter consumer
> --------------------------------------------
>                 Key: AMQ-3697
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.5.1
>         Environment: SunOS 5.10 Generic_142909-17 sun4v sparc SUNW,T5140
>            Reporter: William
>            Priority: Critical
> I am using ActiveMQ 5.5.1 and sometimes messages are not dispatched to connected consumers.

> A single broker is used. No transaction and no persistence is used for message delivery.
Message consumers are spring template made for topic consuption. Optimize acknowledge is enabled
and acknowledgment is auto.
> By Looking at JMX Topic MBean I can see that messages are received but not dispatched
(and of course non depueued). I noticed that disptatched count was 100 more than dequeue count.
> From JMX : 
> * Received count : 4502
> * Dispatched count : 3756
> * Dequeued count : 3656
> If a start a new consumer on the same topic, the messages are only dispatched to the
new consumer while the older one is still seen as connected (consumer count on the mbean is
2). Once the problem appear the only solution is to restart the consumer or the activemq instance.
> It seems that even if the consumer is seen as connected, messages as not dispatched for
an unknow reason. 
> Which logs can I enable in order to diagnose the problem (on activemq side and/or consumer
side) ? I have already made a thread dump, not thread are blocke

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message