activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavel Grushetzky (JIRA)" <j...@apache.org>
Subject [jira] Updated: (AMQ-2612) Polling consumer (prefetch size = 0) fails to reconnect
Date Wed, 17 Feb 2010 10:42:40 GMT

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

Pavel Grushetzky updated AMQ-2612:
----------------------------------

    Description: 
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.

  was:
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 may shows up during short network interruptions as reconnect message
+ processing stoppage.

See http://old.nabble.com/ActiveMQ-reconnect-issue-with-consumer.prefetchSize%3D0-td27574923.html
for more context.


> Polling consumer (prefetch size = 0) fails to reconnect
> -------------------------------------------------------
>
>                 Key: AMQ-2612
>                 URL: https://issues.apache.org/activemq/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
>         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.


Mime
View raw message