pply
>>> only to consumer endpoints, not producer endpoints. Or, if
>>> transactedInOut
>>> is not being ignored, perhaps it is causing some unexpected behavior?
>>>
>>> A key point about the two routes in your example is that each of the
>>> ro
ansaction in Route 1
>> has committed. So, if you are not seeing any messages in mybadqueue, that
>> implies that the transaction in Route 1 has not committed.
>>
>> Perhaps some part of Route 1 is hanging, thus preventing a commit? Could
>> you
>> clarify a couple o
Claus,
I think 'transferException' option is only available in Camel 2.0? I
have to use 1.6.1...
On Tue, Aug 25, 2009 at 8:50 AM, Claus Ibsen wrote:
> See transferException option on Camel JMS
>
>
> On Tue, Aug 25, 2009 at 5:47 PM, Ilya S wrote:
>> Hi Claus,
>>
>> Yes, I believe I am using reques
See transferException option on Camel JMS
On Tue, Aug 25, 2009 at 5:47 PM, Ilya S wrote:
> Hi Claus,
>
> Yes, I believe I am using request/reply over JMS.
>
> Is there a way to ask Camel to commit a TX at some point in my route?
>
> I just sent a clarification on what I'm actually trying to accom
Hi Claus,
Yes, I believe I am using request/reply over JMS.
Is there a way to ask Camel to commit a TX at some point in my route?
I just sent a clarification on what I'm actually trying to accomplish:
if some endpoint in the middle failed, I would the the error to be
propagated back to the origi
ndpoint do? Could it be hanging (thus
> preventing a commit)?
>
> 3. What happens when you remove the transactedInOut="true" setting? I
> suspect that this setting is incorrect and might cause problems.
>
> -
> Cheers,
> Fintan
>
>
>
> --
> View this message in context:
> http://www.nabble.com/JMS-transactions-between-multiple-routes-tp25126004p25130955.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
>
e transactedInOut="true" setting? I
suspect that this setting is incorrect and might cause problems.
-
Cheers,
Fintan
--
View this message in context:
http://www.nabble.com/JMS-transactions-between-multiple-routes-tp25126004p25130955.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Hi
Are you doing request/reply over JMS and want to do that with transactions?
If so that is not possible as messages are not commited to the JMS
queue before the TX is comitted.
On Tue, Aug 25, 2009 at 1:55 AM, Ilya S wrote:
> Hi All,
>
> I'm using Camel 1.6.1 (cannot use 2.0) , with Spring 2.
Hi All,
I'm using Camel 1.6.1 (cannot use 2.0) , with Spring 2.5.6, and ActiveMQ 5.2.
I'm trying to set up Transaction Manager so that my transactions are
rolled back on error.
Here is my camel xml config adopted from the examples:
=
