You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@activemq.apache.org by "Joe Roberts (JIRA)" <ji...@apache.org> on 2012/08/23 22:12:42 UTC

[jira] [Resolved] (AMQ-3948) Multiple consumers retrieving same message from ActiveMQ

     [ https://issues.apache.org/jira/browse/AMQ-3948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joe Roberts resolved AMQ-3948.
------------------------------

    Resolution: Not A Problem

Problem found in our application, not ActiveMQ.
                
> Multiple consumers retrieving same message from ActiveMQ
> --------------------------------------------------------
>
>                 Key: AMQ-3948
>                 URL: https://issues.apache.org/jira/browse/AMQ-3948
>             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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira