I figured out what the problem was, and the problem wasn't with Camel, it was
me. Was doing something stupid in my web service that was causing the
problem. Thanks so much for the quick responses and feedback.
Best Regards,
Aaron
From: Aaron Doyl
my properties values did not display correctly, they are
messageQueueURI=tcp://localhost:61616?jms.prefetchPolicy.queuePrefetch=1
loaderServiceURI=spring-ws:http://localhost:8080/LoaderService
From: Aaron Doyle
To: "users@camel.apache.org"
Se
that
turns SOAP faults into exceptions,
and allow Camel error handler to react then.
On Mon, Oct 3, 2011 at 2:16 PM, Aaron Doyle wrote:
> Hello,
>
> That did not seem to help fix my problem. If I change my route to the
> following, the exception is caugh
wn.) If I run
with 1 consumer, it runs without exceptions.
-Aaron
From: Claus Ibsen
To: users@camel.apache.org; Aaron Doyle
Sent: Monday, October 3, 2011 3:48 AM
Subject: Re: Exception not getting caught and multiple consumers getting the
same message
Hi
You n
nd multiple consumers getting the
same message
Hi
Can you post the XML so its readable :)
On Sat, Oct 1, 2011 at 6:40 PM, Aaron Doyle wrote:
> I have a small route that reads from an activemq queue and sends the message
> to a bean, a service client that calls a web service, and am experie
I have a small route that reads from an activemq queue and sends the message to
a bean, a service client that calls a web service, and am experiencing a few
issues. The onException configuration doesn't seem to get called when the bean
throws an exception, and it seems like some of my concurren
