Return-Path: 
 <users-return-47992-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 75B2910ACB
	for <apmail-camel-users-archive@www.apache.org>;
 Thu,  3 Apr 2014 11:21:51 +0000 (UTC)
Received: (qmail 12107 invoked by uid 500); 3 Apr 2014 11:21:49 -0000
Delivered-To: apmail-camel-users-archive@camel.apache.org
Received: (qmail 11769 invoked by uid 500); 3 Apr 2014 11:21:47 -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 11761 invoked by uid 99); 3 Apr 2014 11:21:45 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Apr 2014 11:21:45 +0000
X-ASF-Spam-Status: No, hits=2.3 required=5.0
	tests=SPF_SOFTFAIL,URI_HEX
X-Spam-Check-By: apache.org
Received-SPF: softfail (nike.apache.org: transitioning domain of
 saran.shajan@gmail.com does not designate 216.139.236.26 as permitted sender)
Received: from [216.139.236.26] (HELO sam.nabble.com) (216.139.236.26)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Apr 2014 11:21:39 +0000
Received: from [192.168.236.26] (helo=sam.nabble.com)
	by sam.nabble.com with esmtp (Exim 4.72)
	(envelope-from <saran.shajan@gmail.com>)
	id 1WVfhu-0003f2-1X
	for users@camel.apache.org; Thu, 03 Apr 2014 04:21:18 -0700
Date: Thu, 3 Apr 2014 04:21:18 -0700 (PDT)
From: Arthanarisamy Annamalai <saran.shajan@gmail.com>
To: users@camel.apache.org
Message-ID: <1396524078038-5749722.post@n5.nabble.com>
Subject: Handling EJB Timeout
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org

To handle timeout on client side for EJB service call, i used
Future<Exchange> and had set time out time over future object. Having this,
both success and time out cases are working fine.

But the problem here is when i take thread dump i could see that the thread
is in waiting state.
When i manually stop and start producer template there are no threads in
waiting state. As per camel guidelines if i allow Spring to inject Producer
Template, starting, stopping and releasing resources will be handled by
Spring itself, but i am not sure whether the resources are released as the
thread is in waiting state.

Or is there a better way to handle time out? If its a HTTP request,
camel-http component has options to set timeout and not in case of camel-ejb
component.

Any suggestions will be of a great help as we are fine tuning out product's
performance and most of the thread's waiting are related to Camel Producer
Template only.



--
View this message in context: http://camel.465427.n5.nabble.com/Handling-EJB-Timeout-tp5749722.html
Sent from the Camel - Users mailing list archive at Nabble.com.