[
https://issues.apache.org/jira/browse/AMQ-2612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12972296#action_12972296
]
michael cheung commented on AMQ-2612:
-------------------------------------
still doesn't work if i specify my broker url to
failover:(tcp://host:61616?jms.prefetchPolicy.queuePrefetch=1,tcp://s2hb-pmt-stg-svc4:61616?jms.prefetchPolicy.queuePrefetch=1)?randomize=false
When I start my consumer, it doesn't consume any messages. In the activemq web
console, it show zero consumers. But it works if i put queuePrefetch="1"
property in the activemq.xml.
<destinationPolicy>
<policyMap>
<policyEntries>
<policyEntry topic=">" producerFlowControl="true"
memoryLimit="1mb">
<dispatchPolicy>
<roundRobinDispatchPolicy />
</dispatchPolicy>
<pendingSubscriberPolicy>
<vmCursor />
</pendingSubscriberPolicy>
<subscriptionRecoveryPolicy>
<noSubscriptionRecoveryPolicy />
</subscriptionRecoveryPolicy>
</policyEntry>
<policyEntry queue=">" producerFlowControl="true"
memoryLimit="1mb" queuePrefetch="1">
<deadLetterStrategy>
<individualDeadLetterStrategy
queuePrefix="DLQ." useQueueForQueueMessages="true"
/>
</deadLetterStrategy>
<dispatchPolicy>
<roundRobinDispatchPolicy />
</dispatchPolicy>
<subscriptionRecoveryPolicy>
<noSubscriptionRecoveryPolicy />
</subscriptionRecoveryPolicy>
</policyEntry>
</policyEntries>
</policyMap>
</destinationPolicy>
> Polling consumer (prefetch size = 0) fails to reconnect
> -------------------------------------------------------
>
> Key: AMQ-2612
> URL: https://issues.apache.org/jira/browse/AMQ-2612
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, JMS client
> Affects Versions: 5.3.0
> Environment: Reproduced on Windows XP 32 bit and Fedora 12 64bit.
> Reporter: Pavel Grushetzky
> Fix For: 5.4.1
>
> Attachments: AMQ-2612-test.patch
>
>
> Scenario:
> 1. Configure polling consumer (prefetch=0), with onMessage()-style
> processing, e.g. with Spring's DefaultMessageListenerContainer.
> 2. Restart broker.
> 3. Notice consumer does not consumer messages anymore.
> In client application this may show up during short network interruptions as
> reconnect message in logs/console + processing stoppage.
> See
> http://old.nabble.com/ActiveMQ-reconnect-issue-with-consumer.prefetchSize%3D0-td27574923.html
> for more context.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
