Mailing-List: contact issues-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Fri, 9 Mar 2012 19:25:00 +0000 (UTC)
From: "Ashwin Karpe (Work stopped) (JIRA)" <jira@apache.org>
To: issues@camel.apache.org
Message-ID: 
 <557933135.44937.1331321100038.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <955858513.39253.1331225397539.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Work stopped] (CAMEL-5070) Message Loss when using Weighted
 Round Robin LoadBalancer
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Work on CAMEL-5070 stopped by Ashwin Karpe.

> Message Loss when using Weighted Round Robin LoadBalancer
> ---------------------------------------------------------
>
>                 Key: CAMEL-5070
>                 URL: https://issues.apache.org/jira/browse/CAMEL-5070
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-core
>    Affects Versions: 2.9.1
>            Reporter: Nikolaos Dimos
>            Assignee: Ashwin Karpe
>         Attachments: loadbalancer-itest.zip
>
>
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira