activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joe Roberts (JIRA)" <>
Subject [jira] [Commented] (AMQ-3948) Multiple consumers retrieving same message from ActiveMQ
Date Mon, 30 Jul 2012 14:09:34 GMT


Joe Roberts commented on AMQ-3948:

I have tried using ActiveMQ 5.6 and the same issue is seen there. This typically happens when
multiple consumers attempt to retrieve a message at the same time. Our consumers spit out
logs and the logged messages occur within the same second. If the timing is outside of that,
this issue is not seen and messages are retrieved normally. If our client was failing to do
something, I would expect this redelivery to occur all the time. The timing on this also makes
it difficult to lock down in a unit test, though we can try. Would our logs or the activemq
logs be helpful here?
> Multiple consumers retrieving same message from ActiveMQ
> --------------------------------------------------------
>                 Key: AMQ-3948
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.4.3
>         Environment: ActiveMQ 5.4.3 running on 64-bit Windows 7 OS. 64-bit JDK. 
>            Reporter: Joe Roberts
>             Fix For: NEEDS_REVIEWED
>         Attachments: applicationContext-mcp-parallelization-activemq.xml
> We have a java web-service (running in Jetty) that dynamically instantiates an ActiveMQ
queue and send messages to the queue - the messages are integers (i.e. 1, 2, 3, etc). We have
from one to many consumers that read from this queue to process these messages. Each consumer
is started from a single process but each consumer is running in it's own thread or process.
When we have multiple consumers running, they occasionally will pick up the same integer or
message from the queue. This is not desired. If a consumer reads a message, we don't want
other consumers to retrieve that same message. We're fairly new to ActiveMQ but those we're
telling about this issue said it should not be happening. They think it might be that we have
an ActiveMQ configuration issue. Could be we need to set a property to prevent this. Just
looking for some help. I've attached our applicationContext-mcp-parallelization-activemq XML.
We could have configured this incorrectly. We're using the internalAmqConnectionFactory for
this queue.

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