Return-Path: 
 <users-return-25700-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 C57679878
	for <apmail-camel-users-archive@www.apache.org>;
 Tue, 20 Dec 2011 08:54:06 +0000 (UTC)
Received: (qmail 42046 invoked by uid 500); 20 Dec 2011 08:54:06 -0000
Delivered-To: apmail-camel-users-archive@camel.apache.org
Received: (qmail 42010 invoked by uid 500); 20 Dec 2011 08:54: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
Received: (qmail 42002 invoked by uid 99); 20 Dec 2011 08:54:05 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 20 Dec 2011 08:54:05 +0000
X-ASF-Spam-Status: No, hits=1.3 required=5.0
	tests=SPF_PASS,URI_HEX
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of willem.jiang@gmail.com
 designates 209.85.161.173 as permitted sender)
Received: from [209.85.161.173] (HELO mail-gx0-f173.google.com)
 (209.85.161.173)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 20 Dec 2011 08:53:59 +0000
Received: by ggnk1 with SMTP id k1so5535300ggn.32
        for <users@camel.apache.org>; Tue, 20 Dec 2011 00:53:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=message-id:date:from:user-agent:mime-version:to:subject:references
         :in-reply-to:content-type:content-transfer-encoding;
        bh=QQ/AkLi8rgZVbwCwfGR0B7AxjWkDCPYLNxzv7bFraHY=;
        b=NcINxKl+YuDapX+XTL0YJth3HVRyU1B6VYCHzDDnmWXB8yc/Ghk0rQmdpsnzMQEqAs
         Sd1iDrZpAio12y3MfB8MMZDyOuhRqNaaUhNGT0u+a6PfVrc+9LjOG9xQNXlTRZWfpjOj
         jd16iDNneGzKy+BfSm1SMkJJv3lTSGqicOLP8=
Received: by 10.50.184.137 with SMTP id eu9mr1868511igc.9.1324371217990;
        Tue, 20 Dec 2011 00:53:37 -0800 (PST)
Received: from [192.168.0.158] ([123.116.34.236])
        by mx.google.com with ESMTPS id gf6sm23162444igb.1.2011.12.20.00.53.32
        (version=SSLv3 cipher=OTHER);
        Tue, 20 Dec 2011 00:53:36 -0800 (PST)
Message-ID: <4EF04D08.9070508@gmail.com>
Date: Tue, 20 Dec 2011 16:53:28 +0800
From: Willem Jiang <willem.jiang@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7;
 rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: users@camel.apache.org
Subject: Re: Intercept issue - need help
References: <1324054195470-5080816.post@n5.nabble.com>
 <6922003085298320214@unknownmsgid> <1324062196995-5081107.post@n5.nabble.com>
 <CAGgTx3i8+gUzve7OW4zMhtE4Zsa0Jey5b1OZH-mALiSUyX-AgA@mail.gmail.com>
 <1324063447408-5081145.post@n5.nabble.com>
 <CAGgTx3hvmPWRTy+h-imBEqqXdf0E50NDzFJqHfJN3+JwLbU0Zg@mail.gmail.com>
 <1324305297142-5086304.post@n5.nabble.com>
 <1324318433275-5086885.post@n5.nabble.com>
 <-5520844275741051114@unknownmsgid>
In-Reply-To: <-5520844275741051114@unknownmsgid>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org

<intercept>

<to uri="seda:trace" />

</intercept>

<route>

<from uri="seda:trace" />

<bean ref="marsTraceProcessor" method="traceExchange"/>

<log message="Persisting to Trace to Database"/>

<to uri="jpa://com.vzw.fp.mars.entities.MarsTracerEntity"/>

</route>

The interceptor will affect the route, I think the we should put the 
trace part into the inteceptor block like this.

<intercept>

<bean ref="marsTraceProcessor" method="traceExchange"/>

<log message="Persisting to Trace to Database"/>

<to uri="jpa://com.vzw.fp.mars.entities.MarsTracerEntity"/>

</intercept>

On Tue Dec 20 06:25:07 2011, Raul Kripalani wrote:
> Hi Ebe,
>
> Camel delegates the connection handling to the JPA framework. Your
> JDBC driver may be using a connection pool or something. All that is
> handled by the JPA EntityManager, so you may want to look at options
> to configure the behaviour regarding the connection.
>
> As to the file not being moved when processing finishes, can you place
> an OnComplete block that sends to a log endpoint with showAll=true and
> paste the logging output?
>
> Are there any exceptions occurring?
>
> Regards,
> Raul.
>
> On 19 Dec 2011, at 18:14, ebinsingh<ebenezer.singh@verizonwireless.com>  wrote:
>
>> Looks like the JPA connection does not close after persisting the data in the
>> database. Not sure how to resolve this.
>>
>> Appreciate any help.
>>
>> --
>> View this message in context: http://camel.465427.n5.nabble.com/Intercept-issue-need-help-tp5080816p5086885.html
>> Sent from the Camel - Users mailing list archive at Nabble.com.
>



-- 
Willem
----------------------------------
FuseSource
Web: http://www.fusesource.com
Blog:    http://willemjiang.blogspot.com (English)
         http://jnn.javaeye.com (Chinese)
Twitter: willemjiang 
Weibo: willemjiang