camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (Commented) (JIRA)" <>
Subject [jira] [Commented] (CAMEL-5070) Message Loss when using Weighted Round Robin LoadBalancer
Date Sat, 10 Mar 2012 08:58:56 GMT


Claus Ibsen commented on CAMEL-5070:

See the asyncConsumer option on the JMS component
> Message Loss when using Weighted Round Robin LoadBalancer
> ---------------------------------------------------------
>                 Key: CAMEL-5070
>                 URL:
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-core
>    Affects Versions: 2.9.1
>            Reporter: Nikolaos Dimos
>            Assignee: Ashwin Karpe
>             Fix For: 2.8.5, 2.10.0, 2.9.2
>         Attachments:
> 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?

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message