You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2010/09/17 11:42:40 UTC

[jira] Commented: (CAMEL-3125) When the fetching of a feed causes, polling continues endlessly, flooding the logs and creating unwanted network load.

    [ https://issues.apache.org/activemq/browse/CAMEL-3125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61890#action_61890 ] 

Claus Ibsen commented on CAMEL-3125:
------------------------------------

So you impl will invoke onError the first 2 times, and then the 3rd time it invokes onSuspend. Then when its in the future it will invoke onError.
The misses is never reset.

Also this is a stateful implementation which mean you should use a new instance on each different consumer.


> When the fetching of a feed causes, polling continues endlessly, flooding the logs and creating unwanted network load.
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-3125
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-3125
>             Project: Apache Camel
>          Issue Type: Wish
>          Components: camel-rss
>    Affects Versions: 2.4.0
>         Environment: ubuntu 10.4
> java 6
>            Reporter: Ernst Bunders
>         Attachments: LimitingPollingConsumerPollStrategy.java
>
>
> The problem is with the default implementation of org.apache.camel.spi.PollingConsumerPollStrategy: org.apache.camel.impl.DefaultPollingConsumerPollStrategy
> When an error occurs rollback() is called, and this method just logs the error and returns false, which means the polling will not be retried for that execution of the run() method. 
> This means it will be retried after the delay.
> I created an implementation that suspends the Consumer, which seems like acceptable default behavior. It also allows for extension and adding some hooks for custom stuff. In order for that to be useful it should be made easier to set your own PollingConsumerPollStrategy implementation.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.