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 gert.vanthienen@gmail.com
 designates 209.85.219.158 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=dWUCh7LESe0HUBiRH+JSDFyBLN39pkxN0oZyN9M4+SDBEf7TqFLqpFbNmhNysxN5JO
         p4pavs5pdERJvQ72LIHC5HAOZ5zWB7ClZy/mLxXRbWhYi8HgYqWQYGvQjk3RejNQB5ix
         tBoZ2Gr3L2/jBlr/LoHHVFiSHZoxWY9K0j6HU=
MIME-Version: 1.0
In-Reply-To: <22628026.post@talk.nabble.com>
References: <22628026.post@talk.nabble.com>
Date: Mon, 23 Mar 2009 13:11:43 +0100
Message-ID: <67a6ab030903230511l92e9f9bm873cfbbac0a13e78@mail.gmail.com>
Subject: Re: What If JBI sendSync() Never Returns?
From: Gert Vanthienen <gert.vanthienen@gmail.com>
To: users@camel.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

L.S.,

When sending a JBI MessageExchange to another JBI endpoint from Camel,
the servicemix-camel component will the same messaging style as is
used in the Camel route.  If your Camel route contains e.g. a seda:
endpoint, Camel will start using async messaging and it will also use
an async JBI MessageExchange to communicate with the JBI NMR.  This
still doesn't handle the use case where the service fails to respond
at all (although it will usually not hang, it's far more likely to
return an Error status).

However, your suggestion for improving the Camel component to allow
sync messaging with a message timeout is a very interesting one, so
we'd really appreciate a JIRA issue for it at
https://issues.apache.org/activemq/browse/SMXCOMP.  Since you
obviously know your way around the source code, don't hesitate to try
doing a patch -- just let us know if you need any help...

Regards,

Gert Vanthienen
------------------------
Open Source SOA: http://fusesource.com
Blog: http://gertvanthienen.blogspot.com/


2009/3/20 Bob Pollack <robert_h_pollack@yahoo.com>:
>
> Does anyone know of a way to set a timer for JBI endpoints? If I make a
> request of a JBI service (by something like to ("jbi:endpoint:foo"), the
> call to the JBI endpoint seems to be made as DeliveryChannel.sendSync
> (message), with no timeout. If the target JBI service doesn't respond (le=
t's
> say it crashes), the Camel route seems to hang forever.
>
> When I look at the code, the JBI call seems to be done by
> org.apache.servicemix.common.endpoints.SimpleEndpoint, which doesn't even
> contain a sendSync() call with a timeout. So I conclude that there's no w=
ay
> for Camel to ask for one.
>
> Should this be submitted as an enhancement request? (If so, can someone t=
ell
> me where?) Or does someone have a Camel workaround or a Java thread
> solution?
>
> (This is related to
> http://www.nabble.com/Servicemix-Camel-problem---ToJbiProcessor-hangs-tp1=
8651622p18651622.html
> a similar problem =A0that has already been posted here. But the previous
> problem concerned a JBI-JMS interaction that appears to have been solved =
by
> changing the JMS logic. I'm interested in a solution that gives me some k=
ind
> of timeout when the target JBI component fails to respond for any reason
> whatsoever.)
>
> Thanks in advance to anyone who can help.
> --
> View this message in context: http://www.nabble.com/What-If-JBI-sendSync%=
28%29-Never-Returns--tp22628026p22628026.html
> Sent from the Camel - Users (activemq) mailing list archive at Nabble.com=
.
>
>