That's pretty close to what I want to do, but the
ThrottlingInflightRoutePolicy appears to throttle at the end of the route
(or so it seems from the 'onExchangeDone' method). I think I could make it
work by writing my own policy to check the DB in the 'onExchangeBegin'
method.
Thanks Claus!
Cl
My application will send requests to a remote system via XML-RPC, but the
remote system does not queue or throttle requests in any way -- it is fairly
trivial for my application to overload the remote system and make it crash.
I don't think that the throttler pattern will work for my intended usa
and I probably should have used it from the
beginning.
Thanks for all your help Claus!
Claus Ibsen-2 wrote:
>
> On Wed, Apr 14, 2010 at 6:51 PM, dnn wrote:
>>
>> This one just won't die :)
>>
>> I've got the same issue, but caused in a slightly diffe
t;
> On Fri, Apr 9, 2010 at 8:46 PM, dnn wrote:
>>
>> Works for me too using trunk. It looks like an automated build pulls the
>> trunk at midnight and deploys it to 2.3-SNAPSHOT in maven, so I should be
>> able to start using it from mvn tomorrow. When is 2.3.0 sla
Works for me too using trunk. It looks like an automated build pulls the
trunk at midnight and deploys it to 2.3-SNAPSHOT in maven, so I should be
able to start using it from mvn tomorrow. When is 2.3.0 slated for release?
Thanks for all the hard work. You guys make a great product!
Claus Ib
Thanks for the quick replies!
Willem--
This is a rather trivial test case - in my "real" routes I definitely
require the tags. It does appear that using transacted IS
setting up a new TransactionErrorHandler; it's just not grabbing the global
onException handlers as I expected...
Claus--
Cam
I am trying to use global onException handling with a transacted route.
According to the everything I've read, the following should print the "HEY I
GOT AN EXCEPTION" message:
java.lang.Exception
I would imagine that when "som
