;>> it then travels down a error route.
>>>>>
>>>>> This worked in the past. However, recently I found that the messages
>>>>> no
>>>>> longer make it to the DLQ. I have been updating my Camel 2.0 source
>>>>> from
&
amel 2.0 source
>>>> from
>>>> SVN every so often and rebuilding. I am wondering if something changed
>>>> that
>>>> I need to take in to account.
>>>>
>>>> Currently it seems the transaction does a rollback and redelivery five
>>> it
>>> go back to the original queue. Do I need to change a configuration to
>>> support the newer 2.0 build of Camel that I am now using?
>>>
>>
>> Can you paste your route.
>> And run with DEBUG/TRACE logging for org.apache.camel.spring as
gt;>
>>
>
>
>
> --
> Claus Ibsen
> Apache Camel Committer
>
> Open Source Integration: http://fusesource.com
> Blog: http://davsclaus.blogspot.com/
> Twitter: http://twitter.com/davsclaus
>
>
Here is some of the debug logging:Here is some of the debug logging:
--
View this message in context:
http://www.nabble.com/Camel-2.0-Transaction-Rollback-tp24534561p24540640.html
Sent from the Camel - Users mailing list archive at Nabble.com.
el that I am now using?
>
Can you paste your route.
And run with DEBUG/TRACE logging for org.apache.camel.spring as the
Camel transacted error handler lives there.
It should indicate when its rolling back etc.
> Thanks.
> --
> View this message in context:
> http://www.nabble.com/Ca
. Then the message disappears. It does not go to a DLQ, nor does it
go back to the original queue. Do I need to change a configuration to
support the newer 2.0 build of Camel that I am now using?
Thanks.
--
View this message in context:
http://www.nabble.com/Camel-2.0-Transaction-Rollback
