[jira] [Closed] (AMQ-4827) Set jms.queuePrefetch=1 Causes Messages To Be Stuck in Queue

["Timothy Bish (JIRA)" <ji...@apache.org>]

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

Timothy Bish closed AMQ-4827.
-----------------------------

    Resolution: Not A Problem

Issue can be resolved with the AbortSlowAckConsumerStrategy or by setting prefetch to zero.  Update page adding a link to the API docs for the strategy.  

> Set jms.queuePrefetch=1 Causes Messages To Be Stuck in Queue
> ------------------------------------------------------------
>
>                 Key: AMQ-4827
>                 URL: https://issues.apache.org/jira/browse/AMQ-4827
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.7.0, 5.8.0
>            Reporter: Yung Lai
>
> Configuration:
> connectionUri=tcp://localhost:61616?jms.prefetchPolicy.queuePrefetch=1&keepAlive=true
> activemq.conf is default with no changes
> Scenario:
> Sent 7 different messages to the same queue. With prefetch=1 about 1 or 2 messages would get stuck in the queue everytime. After a restart of activemq the messages that were stuck in queue would be processed.
> With cachingConsumers=false the messages would not get stuck.
> We need cachingConsumers for better performance so setting it to false is not an option for us.
> Here is a thread that is very similar to the issue.
> http://activemq.2283324.n4.nabble.com/Messages-stuck-in-queue-td3244342.html
> Thank you for your time and consideration.



--
This message was sent by Atlassian JIRA
(v6.1#6144)