Yay!
2009/4/2 Claus Ibsen :
> Hi
>
> The default error handler is now changed in Camel 2.0.
>
> On Wed, Apr 1, 2009 at 11:58 AM, Claus Ibsen wrote:
>> On Wed, Apr 1, 2009 at 11:51 AM, Roman Kalukiewicz
>> wrote:
>>> I would definitely support #1.
>>>
>>> #3 is not so good as a default one becaus
Hi
The default error handler is now changed in Camel 2.0.
On Wed, Apr 1, 2009 at 11:58 AM, Claus Ibsen wrote:
> On Wed, Apr 1, 2009 at 11:51 AM, Roman Kalukiewicz
> wrote:
>> I would definitely support #1.
>>
>> #3 is not so good as a default one because it can cause some side effects
>> like w
On Wed, Apr 1, 2009 at 11:51 AM, Roman Kalukiewicz
wrote:
> I would definitely support #1.
>
> #3 is not so good as a default one because it can cause some side effects
> like when you use in-out JMS endpoint. If nothing listens to the queue, then
> you will end up with 6 messages in request queue
I would definitely support #1.
#3 is not so good as a default one because it can cause some side effects
like when you use in-out JMS endpoint. If nothing listens to the queue, then
you will end up with 6 messages in request queue instead of one (assuming
you don't use transactions).
BTW Last tim
L.S.,
I'm in favor of disabling error handling by default as well. People
should really configure this to suit their environment. And with my
ServiceMix hat on, this would be a big improvement as well -- error
handling should be configured there based on the properties of the
given message flow
On Wed, Apr 1, 2009 at 6:40 AM, Willem Jiang wrote:
> +1 for 1) and 3).
> We need to find a better way to handle the TX with Spring by default.
For the TX part people would like the *onException* feature to be
possible as well.
We have this kind of "trick" where you can use the DLC and let the TX
+1 for 1) and 3).
We need to find a better way to handle the TX with Spring by default.
Willem
Claus Ibsen wrote:
> Hi
>
> As we work on the Camel 2.0 I would suggest that we start a discussion
> what should be the preferred error handler defaults in Camel 2.0.
> What we currently have is the DL
+1 for disabled by default.
On Tue, Mar 31, 2009 at 3:21 AM, Claus Ibsen wrote:
> Hi
>
> As we work on the Camel 2.0 I would suggest that we start a discussion
> what should be the preferred error handler defaults in Camel 2.0.
> What we currently have is the DLC is default and it does 6 retries
1) +1
Hadrian
On Mar 31, 2009, at 1:51 AM, Claus Ibsen wrote:
Hi
As we work on the Camel 2.0 I would suggest that we start a discussion
what should be the preferred error handler defaults in Camel 2.0.
What we currently have is the DLC is default and it does 6 retries
with 1 sec apart and the
I'm liking 1).
If endpoints were transacted by default (which is probably what folks
really want), then having no error handler would be fine - so long as
the consumer managed the transaction & rollback?
BTW having the (say) JmsEndpoint auto-create a JmsTransactionManager
if none is configured is
Based on the routes I have configured we are either doing a custom
configuration or turning it off.
So +1 for disabled by default.
- Original message -
From: "Claus Ibsen"
To: dev@camel.apache.org
Date: Tue, 31 Mar 2009 07:51:11 +0200
Subject: [DISCUSS] - Default error handle
Hi
As we work on the Camel 2.0 I would suggest that we start a discussion
what should be the preferred error handler defaults in Camel 2.0.
What we currently have is the DLC is default and it does 6 retries
with 1 sec apart and then just log an ERROR and ends the exchange.
We have 3 different err
12 matches
Mail list logo
