[CAMEL-5070] Message Loss when using Weighted Round Robin LoadBalancer

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.9.1
• Fix Version/s: 2.8.5, 2.9.2, 2.10.0
• Component/s: camel-core
• Estimated Complexity: Unknown
• Assignee: Ashwin J. Karpe
• Reporter: Nikolaos Dimos
• Created: 08/Mar/12 16:48
• Updated: 10/Mar/12 09:25
• Resolved: 09/Mar/12 19:25

Description

chooseProcessor method accesses resources in a non synchronized fashion. This leads in errors during loadbalancing and as a result messages are lost. I have created a project that provides an integration test (using karaf 2.2.5 and a custom command to check messages of the activemq broker) with a custom weighted round robin loadbalancer that "seems" to solve the issue of lost messages.

The problem with the provided solution is that when messages are dequeued from the second stage of queues (queues1, 2 and 3) in custom-loadbalancer-route subproject the jmsconsumer threads also block (checked this using profiler). I would expect only the jmsconsumer threads of the first queue (initial.queue) to block waiting for the synchronized chooseProcessor method. Any clues on why this happens?