[CAMEL-6635] PollingConsumer from a scheduled consumer such as file/ftp can use a regular thread pool instead of being scheduled

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Abandoned
• Fix Version/s: 2.12.0
• Component/s: camel-core
• Estimated Complexity: Unknown
• Assignee: Claus Ibsen
• Reporter: Claus Ibsen
• Created: 14/Aug/13 08:13
• Updated: 14/Aug/13 14:55
• Resolved: 14/Aug/13 14:55

Description

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.