[CAMEL-10215] EventDrivenPollingConsumer is not thread safe when used with ConsumerCache

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.18.0
• Fix Version/s: 2.16.4, 2.17.3, 2.18.0
• Component/s: camel-core
• Patch Info: Patch Available
• Estimated Complexity: Unknown
• Assignee: Claus Ibsen
• Reporter: Siddharth Sharma
• Created: 01/Aug/16 22:43
• Updated: 02/Aug/16 06:49
• Resolved: 02/Aug/16 06:49

Description

For static endpoints, if DefaultConsumerTemplate#receive() is used, ConsumerCache will return the cached instance of PollingConsumer for every thread part of parallel processing of split/aggregate.

Now, if EventDrivenPollingConsumer is used, returning same cache instance causes race condition in receive and receive(long) as the methods are not thread safe. The ordering of beforePoll, poll and afterPoll needs to be synchronized, otherwise the consumer might end up being suspended in afterPoll and the client whose beforePoll couldn't wake up the suspended thread will get no data.

Issue Links

• links to: GitHub Pull Request #1099