You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Timothy Bish (JIRA)" <ji...@apache.org> on 2012/06/01 16:45:23 UTC

[jira] [Closed] (AMQ-3691) Messages left in the queue unconsumed

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

Timothy Bish closed AMQ-3691.
-----------------------------

    Resolution: Incomplete

Couldn't get the supplied tests to reproduce the issue.  Recommend you try out a new broker version.  If the problem still persists you should try and make the test case maven runnable so it easier to work with.  
                
> Messages left in the queue unconsumed
> -------------------------------------
>
>                 Key: AMQ-3691
>                 URL: https://issues.apache.org/jira/browse/AMQ-3691
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.5.0
>         Environment: Linux
>            Reporter: bhaskar annamalai
>              Labels: performance
>         Attachments: files.zip
>
>
> We use activemq with spring integration in our application. When we did some performance tests on activemq some of the messages are not consumed and remain in the queue. These messages are never consumed at all. This can be easily reproduced by have the producer in one applicaiton context and the receiver in another. Attached a very simple test case that loads two application contexts(one containing the producer and another the consumer). For most of the runs of the test case we see some messages staying in the queue unconsumed. These are not consumed in the next run.

--
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