camel-issues 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-6635) PollingConsumer from a scheduled consumer such as file/ftp can use a regular thread pool instead of being scheduled
Date Wed, 14 Aug 2013 14:56:48 GMT

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

Claus Ibsen resolved CAMEL-6635.
--------------------------------

    Resolution: Unresolved

Darn the polling consumer logic wasn't too well equipped for this kind. Had to revert to use
the old way to allow picking up late files that arrives later when the poll starts.
                
> PollingConsumer from a scheduled consumer such as file/ftp can use a regular thread pool
instead of being scheduled
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-6635
>                 URL: https://issues.apache.org/jira/browse/CAMEL-6635
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-core
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>             Fix For: 2.12.0
>
>
> Due the recent SPI which allows to plugin a different scheduler we can improved this
and use a non scheduled thread pool, which avoids the suspend/resume and run for at least
one poll "hack" we have today in the codebase.
> Instead we can use a regular thread pool as the scheduler, and then submit the task on
demand when receive() is called on the PollingConsumer API.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message