Return-Path: 
 <issues-return-14109-apmail-camel-issues-archive=camel.apache.org@camel.apache.org>
X-Original-To: apmail-camel-issues-archive@minotaur.apache.org
Delivered-To: apmail-camel-issues-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 6FDCC10846
	for <apmail-camel-issues-archive@minotaur.apache.org>;
 Thu, 21 Nov 2013 19:37:35 +0000 (UTC)
Received: (qmail 26774 invoked by uid 500); 21 Nov 2013 19:37:35 -0000
Delivered-To: apmail-camel-issues-archive@camel.apache.org
Received: (qmail 26749 invoked by uid 500); 21 Nov 2013 19:37:35 -0000
Mailing-List: contact issues-help@camel.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:issues-help@camel.apache.org>
List-Unsubscribe: <mailto:issues-unsubscribe@camel.apache.org>
List-Post: <mailto:issues@camel.apache.org>
List-Id: <issues.camel.apache.org>
Reply-To: dev@camel.apache.org
Delivered-To: mailing list issues@camel.apache.org
Received: (qmail 26741 invoked by uid 99); 21 Nov 2013 19:37:35 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 21 Nov 2013 19:37:35 +0000
Date: Thu, 21 Nov 2013 19:37:35 +0000 (UTC)
From: "Claus Ibsen (JIRA)" <jira@apache.org>
To: issues@camel.apache.org
Message-ID: <JIRA.12680319.1384965241798.10087.1385062655331@arcas>
In-Reply-To: <JIRA.12680319.1384965241798@arcas>
References: <JIRA.12680319.1384965241798@arcas>
Subject: [jira] [Commented] (CAMEL-6988) 2.12.1 caches groovy call -
 resulting with previous caller state
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


    [ https://issues.apache.org/jira/browse/CAMEL-6988?page=3Dcom.atlassian=
.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1382=
9262#comment-13829262 ]=20

Claus Ibsen commented on CAMEL-6988:
------------------------------------

CAMEL-6340 was also introduced in Camel 2.11.1. Are you sure its that versi=
on? Can you double check.


> 2.12.1 caches groovy call - resulting with previous caller state
> ----------------------------------------------------------------
>
>                 Key: CAMEL-6988
>                 URL: https://issues.apache.org/jira/browse/CAMEL-6988
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-groovy
>    Affects Versions: 2.12.1
>         Environment: same results using java 7 on osx, ubuntu, and windoz=
e
>            Reporter: Terry Walters
>
> 2.12.1
> Works
> {code}
>         <simple>"${body.subOrderName}Endpoint"</simple>
> {code}
> Fails=20
> {code}
>          <groovy>"${request.body.subOrderName}Endpoint"</groovy>
> {code}
> 2.11.1
> Works
> {code}
>         <simple>"${body.subOrderName}Endpoint"</simple>
> {code}
> Works
> {code}
>         <groovy>"${request.body.subOrderName}Endpoint"</groovy>
> {code}
> *Fails by returning a previous calls result for subOrderName.=20
> To reproduce you must make several calls in a timely manner with differen=
t bean data (OGNL/subOrderName).
> Route:
> {code}
> ...
> <setHeader headerName=3D"RSSX_ORDER_ROUTING_SLIP">
> <groovy>return "${request.body.subOrderName}Endpoint"</groovy>
> </setHeader>
> <!-- Route the order by the routing slip header -->
> <routingSlip>
> <header>RSSX_ORDER_ROUTING_SLIP</header>
> </routingSlip>
> ...
> {code}
> Log:
> 1st execution
> Before set header:    UpdatePortIn
> After set header:   RSSX_ORDER_ROUTING_SLIP=3DUpdatePortInEndpoint
> 2nd execution (in a timely manner =E2=80=93 exposing a LRU Cache issue?)
> Before set header: ResellerAddSubscriberPortIn
> After set header:    RSSX_ORDER_ROUTING_SLIP=3DUpdatePortInEndpoint
> Same logic works in 2.11.1
> Additionally this does not appear OGNL related:
> I just ran into the case where      =20
> {code}
> <setHeader headerName=3D"RSSX_ORDER_ROUTING_SLIP">
>         <groovy>"${request.body.getSubOrderName()}Endpoint"</groovy>
>       </setHeader>
> {code}
> returns the cached subOrderName from the previous transaction
> So this appears to be isolated to the <groovy> component changes (LRU Cac=
he?) that were introduced in 2.12.1



--
This message was sent by Atlassian JIRA
(v6.1#6144)