Return-Path: 
 <users-return-59668-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 46C3F10412
	for <apmail-camel-users-archive@www.apache.org>;
 Tue,  8 Mar 2016 06:03:07 +0000 (UTC)
Received: (qmail 59382 invoked by uid 500); 8 Mar 2016 06:03:06 -0000
Delivered-To: apmail-camel-users-archive@camel.apache.org
Received: (qmail 59289 invoked by uid 500); 8 Mar 2016 06:03:06 -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
Delivered-To: moderator for users@camel.apache.org
Received: (qmail 80536 invoked by uid 99); 8 Mar 2016 01:15:06 -0000
X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org
X-Spam-Flag: NO
X-Spam-Score: 4.536
X-Spam-Level: ****
X-Spam-Status: No, score=4.536 tagged_above=-999 required=6.31
	tests=[DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_ENVFROM_END_DIGIT=0.25,
	KAM_ASCII_DIVIDERS=0.8, NML_ADSP_CUSTOM_MED=1.2,
	RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.972, URI_HEX=1.313]
	autolearn=disabled
Date: Mon, 7 Mar 2016 18:15:00 -0700 (MST)
From: sjlee7373 <sjlee7373@gmail.com>
To: users@camel.apache.org
Message-ID: <1457399700982-5778717.post@n5.nabble.com>
Subject: Camel jetty Dead Lock and Threadfull based ServiceMix 5.3.0
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi, 

I have a problem with camel in ServiceMix.

I made webservice throught camel-jetty, camel-recipentlist in servicemix.
This package is good performance but resource lock and thread full ocurred
it. This system process 40 Call per second.

The problem is that pool threads aren't released properly sometimes. After 
a few hours following the start of an application I can see using jstack 
tool that some threads are stuck in a WAITING state: 

configuration is as follows: 
- servicemix 5.3.0
- camel 2.13.2
- using component (camel-jetty , camel-recipentlist  based Spring DSL)

-------------- SOURCE
----------------------------------------------------------------------
<route customId="true" >
    <from uri="direct:giop_addr_async">
        <recipentList>
             
<simple>jetty://http://api.host.lm?x=${header.x}&amp;y=${header.y}</simple>
        </recipentList>
        <bean ref="soapDecode" method="userDecode"/>
        <to uri="direct:sendEndPoint">
</route>

<route customId="true>
        <from uri="direct:sendEndPoint">
        <to uri="jetty://http://resultMap?httpClient.soTimeout=80000"/>
</route>

-------------- LOG
---------------------------------------------------------------------------
ps -eLf  | wc -l --> 32500

"CamelJettyClient(0x3d0b240d)-26916" damen prio=10 tid=0x000000000ff69800
nid =0x10ef wating on condition [0x00002b4b3ba3f0000]
   java.lang.Thread.State: TIMED_WAITNG(parking)
     at sun.misc.Unsafe.park(Native Method)
 - parging to wati for <0x000000006f13f19b0> (a
java.util.concurrent.locks.AbstractQueuedsynchronizer$ConditionObject)
 at java.util.concurrent.locks.LocsSupport.parkNanos(LockSupport,java:226)
 at
org.eclipse.jetty.util.BlockingArrayQueue.poll(BlockingArrayQueue.java:342)
 at
org.eclipse.jetty.util.thread.QueuedThreadPool.idleJobPoss(QueuedThreadPool.java:526)
 at
org.eclipse.jetty.tuil.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:572)
 atjava.lnag.thread.run(Thread.java:745)

Above log more than 30000line...... 

Can you suggest what else can be checked? Am I missing something? Or may be 
this is a bug in Camel? 




--
View this message in context: http://camel.465427.n5.nabble.com/Camel-jetty-Dead-Lock-and-Threadfull-based-ServiceMix-5-3-0-tp5778717.html
Sent from the Camel - Users mailing list archive at Nabble.com.