camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (CAMEL-3125) When the fetching of a feed causes, polling continues endlessly, flooding the logs and creating unwanted network load.
Date Fri, 17 Sep 2010 10:52:40 GMT

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

Claus Ibsen resolved CAMEL-3125.
--------------------------------

    Fix Version/s: 2.5.0
       Resolution: Fixed

trunk: 998065.

There is now a {{LimitedPollingConsumerPollStrategy}} which is stateful and supports multiple
consumers, so you can use it for multiple routes.
It will reset if a consumer is being suspended, so when you manually start the consumer its
been reset.

There is a limit option you can set, its by default 3.

> 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
>            Assignee: Claus Ibsen
>             Fix For: 2.5.0
>
>         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.


Mime
View raw message