Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Received-SPF: softfail (athena.apache.org: transitioning domain of
 vinaykumar258@gmail.com does not designate 216.139.236.26 as permitted
 sender)
Date: Mon, 21 Apr 2014 16:31:12 -0700 (PDT)
From: vknfh3 <vinaykumar258@gmail.com>
To: dev@camel.apache.org
Message-ID: <1398123072055-5750407.post@n5.nabble.com>
Subject: Concurrency issue with SEDA component
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi,

I have been facing concurrency issues with SEDA component when using it for
parallely processing 200 or more JSON Messages. Our application should be
able to process and save at least 200 JSONS at a time from each user
simultaneously. The SEDA component route seems to be working fine when only
one user is issuing 200 JSON requests(which will be enclosed in a
JSONArray). I'm running into issues when another user is hitting the same
SEDA route at the same time when the old request from other user is still in
progress. Due to this the output JSON messages are being duplicated and in
some instances getting more JSON messages back than expected!!

Before using SEDA component I tried using split and parallellProcessing and
I ran into similar kind of concurrency issues.
Here is what I have:

from("seda:savesupplyitemsplitter?timeout=0&waitForTaskToComplete=Always&concurrentConsumers=200")
        		.routeId("SaveSupplyItemSplitter")
				.setProperty(SupplyItemRoutesConstants.JSON_ARRAY_MSG, body())
				.process(new Processor() {
					@Override
					public void process(Exchange exchange) throws Exception { 
						List<JSONObject> supplyItemList = (List<JSONObject>)
exchange.getIn().getBody(List.class);
						exchange.setProperty(SupplyItemRoutesConstants.JSON_ARRAY_MSG,
supplyItemList);
						if(!supplyItemList.isEmpty() || supplyItemList.size()!=0){
							JSONObject sItem = supplyItemList.get(0);   //Get the first element
from the List
							exchange.getOut().setBody(sItem); //set the supplyItem as body to the
exchange
						}
					}
				})
				.process(new SupplierNumberProcessor()) 
				.enrich(SupplyItemRoutesConstants.GET_SUPPLIER_GLN_ENDPOINT, new
SupplyItemGLNAggregator())
				.split(simple(SupplyItemRoutesConstants.BODY_STRING), new
SupplyItemDataAggregator())
				.to("direct:savesupplyitem")
           .end();

from("direct:savesupplyitem")    //complex route with lot of external
service calls and calls to other camel enpoints. This route also has lot
processors and aggregators. All the routes that this endpoint calls are
"direct" end points
    . to(some complex processing and saving to database)
.end();   

I have uploaded the code for the above route (direct:savesupplyitem) as
separate file for your reference:
SaveSupplyItemRoutes.txt
<http://camel.465427.n5.nabble.com/file/n5750407/SaveSupplyItemRoutes.txt>  

Do I need to do anything to make it work for multiple users (more than one
user will call the seda endpoint simultaneously)? Am I missing something
here ? Please suggest.

Thanks


--
View this message in context: http://camel.465427.n5.nabble.com/Concurrency-issue-with-SEDA-component-tp5750407.html
Sent from the Camel Development mailing list archive at Nabble.com.