Return-Path: 
 <users-return-57615-apmail-camel-users-archive=camel.apache.org@camel.apache.org>
X-Original-To: apmail-camel-users-archive@www.apache.org
Delivered-To: apmail-camel-users-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 5AF8118879
	for <apmail-camel-users-archive@www.apache.org>;
 Mon, 19 Oct 2015 14:52:16 +0000 (UTC)
Received: (qmail 35894 invoked by uid 500); 19 Oct 2015 14:52:15 -0000
Delivered-To: apmail-camel-users-archive@camel.apache.org
Received: (qmail 35848 invoked by uid 500); 19 Oct 2015 14:52:15 -0000
Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:users-help@camel.apache.org>
List-Unsubscribe: <mailto:users-unsubscribe@camel.apache.org>
List-Post: <mailto:users@camel.apache.org>
List-Id: <users.camel.apache.org>
Reply-To: users@camel.apache.org
Delivered-To: mailing list users@camel.apache.org
Received: (qmail 35837 invoked by uid 99); 19 Oct 2015 14:52:15 -0000
Received: from Unknown (HELO spamd4-us-west.apache.org) (209.188.14.142)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 19 Oct 2015 14:52:15 +0000
Received: from localhost (localhost [127.0.0.1])
	by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org)
 with ESMTP id E5B6AC0429
	for <users@camel.apache.org>; Mon, 19 Oct 2015 14:52:14 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org
X-Spam-Flag: NO
X-Spam-Score: 3.473
X-Spam-Level: ***
X-Spam-Status: No, score=3.473 tagged_above=-999 required=6.31
	tests=[FORGED_HOTMAIL_RCVD2=1.187, SPF_SOFTFAIL=0.972,
	URIBL_BLOCKED=0.001, URI_HEX=1.313] autolearn=disabled
Received: from mx1-eu-west.apache.org ([10.40.0.8])
	by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new,
 port 10024)
	with ESMTP id J4fjljsrGrW9 for <users@camel.apache.org>;
	Mon, 19 Oct 2015 14:52:07 +0000 (UTC)
Received: from mbob.nabble.com (mbob.nabble.com [162.253.133.15])
	by mx1-eu-west.apache.org (ASF Mail Server at mx1-eu-west.apache.org) with
 ESMTP id 1818D20750
	for <users@camel.apache.org>; Mon, 19 Oct 2015 14:52:07 +0000 (UTC)
Received: from msam.nabble.com (unknown [162.253.133.85])
	by mbob.nabble.com (Postfix) with ESMTP id 4A82E17F498A
	for <users@camel.apache.org>; Mon, 19 Oct 2015 07:43:19 -0700 (PDT)
Date: Mon, 19 Oct 2015 07:52:05 -0700 (MST)
From: dermoritz <tanteanni@hotmail.com>
To: users@camel.apache.org
Message-ID: <1445266325345-5772863.post@n5.nabble.com>
Subject: [camel-jdbc] opens one thread per update query until db error
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

I have a route that writes into data base:

from(...).<some preporcessing with split and aggregate>
.threads(10)
.process(createDBquery)
.to(jdbc:db)

My problem is that createDBquery are working in 10 threads (as configured)
but it seems that jdbc-component opens 1 thread per query. So for 1000
exchanges i see 1000 threads. On my oracle db i hit " ORA-01000: maximum
open cursors exceeded" (my db's limit is 1000 cursors)

If i sent 1200 exchanges i hit the error 200 times!

So why so many threads and not 10 at maximum? I want to limit the threads to
10.




--
View this message in context: http://camel.465427.n5.nabble.com/camel-jdbc-opens-one-thread-per-update-query-until-db-error-tp5772863.html
Sent from the Camel - Users mailing list archive at Nabble.com.