Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: pass (nike.apache.org: domain of stasiekk@gmail.com designates
 209.85.192.45 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAGB5yN=kxMZ5qr7qthjP1Sa1dqd13k4pEoxVXXkwL-vTkn+Ugw@mail.gmail.com>
References: 
 <CAP72KA56U1Bk66M_DN9uOm6ntmztwAhht+Gv7b6THfEoJTYiPA@mail.gmail.com>
	<CAGB5yN=kxMZ5qr7qthjP1Sa1dqd13k4pEoxVXXkwL-vTkn+Ugw@mail.gmail.com>
Date: Fri, 30 May 2014 14:01:41 +0200
Message-ID: 
 <CAP72KA5nTQoyVs9PfJFdjFAa0CsOi_fx1=mauLeYNMDMX_Zy3g@mail.gmail.com>
Subject: Re: WireTap Problem
From: =?UTF-8?B?U3RhbmlzxYJhdyBLdcWb?= <stasiekk@gmail.com>
To: users@camel.apache.org
Content-Type: multipart/alternative; boundary=001a11c1299c01fb6304fa9ccf7e

--001a11c1299c01fb6304fa9ccf7e
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi,

I send json in form of String with streamCacheing enabled - since both
Threads only read from stream and it's cached it shouldn't be a problem or
I'm wrong?

Best,
Stanislaw


On Fri, May 30, 2014 at 11:09 AM, Claus Ibsen <claus.ibsen@gmail.com> wrote=
:

> Hi
>
> Beware the wire tap does not do a deep clone of the data, so you may
> have concurrent threads work on the same instance.
>
> You can convert your data to a byte[] or String which would is
> immutable and would not have side effects etc.
>
>
>
> On Fri, May 30, 2014 at 10:54 AM, Stanis=C5=82aw Ku=C5=9B <stasiekk@gmail=
.com>
> wrote:
> > Hi,
> >
> > recently I have experienced a nondeterministic problem while using
> wireTap
> > in my route (Camel 2.13.0).
> >
> > I assume that wireTap should be transparent to main Route proccessing (
> > http://www.enterpriseintegrationpatterns.com/WireTap.html).
> >
> > from("direct:route1").routeId("route1")
> >             .setExchangePattern(ExchangePattern.InOut).streamCaching()
> >             .marshal().json(JsonLibrary.Jackson)
> >
> >
> .wireTap("direct:logIt").to("direct:httpsCall").wireTap("direct:logItAfte=
r")....
> >
> > Wiretap Route:
> >
> >
>  from("direct:logIt").setExchangePattern(ExchangePattern.InOnly).streamCa=
ching().convertBodyTo(String.class).to("file:serverCall/request?autoCreate=
=3Dtrue");
> >
> >
> > The problem appears as I try to call the route several times with the
> same
> > data - sometimes after wireTap the *body is null *causing errors on
> called
> > server.
> >
> > It's a bug in Camel or I'm doing something wrong?
> >
> > Thanks in advance for Your support,
> >
> > Best regards,
> > Stanislaw Kus
>
>
>
> --
> Claus Ibsen
> -----------------
> Red Hat, Inc.
> Email: cibsen@redhat.com
> Twitter: davsclaus
> Blog: http://davsclaus.com
> Author of Camel in Action: http://www.manning.com/ibsen
> hawtio: http://hawt.io/
> fabric8: http://fabric8.io/
>

--001a11c1299c01fb6304fa9ccf7e--