Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Received-SPF: pass (nike.apache.org: domain of bibryam@gmail.com designates
 74.125.82.51 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAKoNANt57+a3BALkKueqX2t_ku1m-ZPjfyg2_K7LZA3=4AFQYQ@mail.gmail.com>
References: 
 <CAJ6eY0bZsw4m2gVVAAdYsR=t92fbLXdB=Vd-pEF1=dnTW9_UQQ@mail.gmail.com>
	<CAKoNANt57+a3BALkKueqX2t_ku1m-ZPjfyg2_K7LZA3=4AFQYQ@mail.gmail.com>
Date: Mon, 25 Feb 2013 11:21:18 +0000
Message-ID: 
 <CAJ6eY0a8T8QnBsKkMYEgGSCwWUqgCjS+r_QiTHFXKVxGLWV64A@mail.gmail.com>
Subject: Re: Seda component not handing over the completions
From: Bilgin Ibryam <bibryam@gmail.com>
To: dev@camel.apache.org
Content-Type: multipart/alternative; boundary=14dae9cc9f966d204804d68abd5d

--14dae9cc9f966d204804d68abd5d
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On 25 February 2013 10:45, Raul Kripalani <raul@evosent.com> wrote:

> Well, it's not safe to execute the completions before the Vm consumer has
> finished processing, because the InputStream could be closed by the time
> the Vm consumer starts processing the exchange.
>
> I agree with Willem that the current implement is correct.
>

I see, you both are right here, but what I actually do is exactly your
example below:


>
> The safest option is to convert the body to a String, and either use the
> threads DSL or inOnly(vm:...) to modify the exchange pattern onwards.
>
>
I've converted the body to a String, and then send the exchange to vm
endpoint using in only patters. At this point I expected to use VM endpoint
as an inmemory VM queue for exchanges, but cannot do that, because the
completions are also handled to that queue. Do I miss something here?

Thanks for your help guys.
Bilgin


> Ra=FAl.
> On 21 Feb 2013 17:13, "Bilgin Ibryam" <bibryam@gmail.com> wrote:
>
> > Hi,
> >
> > I have a route where I consume from a file endpoint and put them in VM
> > endpoint, so that another camel route from different camel app can
> process
> > it a little later asynchronously.
> >
> > The file endpoint has move=3Dprocessed for removing the processed files=
,
> but
> > even the exchanges are delivered to VM endpoint, the exchange is not
> > considered completed, so the original file stays locked and cannot
> process
> > other files before I start the second camel application and process the
> > exchanges from VM endpoint.
> >
> > SEDA has waitForTaskToComplete option, which controls whether the calle=
r
> > should wait for the async task to complete or not before continuing. Bu=
t
> > even when waitForTaskToComplete=3DNever is set, the completions are han=
ded
> > over to VM queue, so it is not possible to complete the exchange.
> >
> > Is there a way to complete the exchange when it is put in VM queue? Or
> > there is a possibility for extending SEDA component with additional
> option
> > for not handling over the completions when waitForTaskToComplete=3DNeve=
r is
> > set?
> >
> > WDYT
> > Bilgin
> >
>

--14dae9cc9f966d204804d68abd5d--