I forwarded my question to activemq-user:
http://old.nabble.com/SecurityException-not-delegated-to-Camel--tp29305408p29305408.html
Thanks,
Holger
Claus Ibsen-2 wrote:
>
> On Fri, Jul 30, 2010 at 1:26 PM, Holger <sihls...@googlemail.com> wrote:
>>
>> Hi Claus,
>>
>> Thanks for your answer.
>>
>> Yet, I know how to configure Active MQ and really intended to have no
>> access
>> to the queue bar2 as a test case.
>>
>> I assumed that Camel would rollback the transaction in this case but
>> unfortunately it does not:
>>
>
> I think this is happening in a lower layer in the JMS broker. You most
> likely need to address this at AMQ and hear how it reacts and whats
> the normal behavior.
>
> Camel *just* uses Spring JMS when you do from("jms") and uses Spring
> TransactionManager. And if an exception is thrown it will rethrow that
> as a RuntimeException back to Spring JMS and hence it will rollback.
>
> So the issue is in the JMS broker and how it enforces this security.
>
>
>> On Wed, Jul 28, 2010 at 12:21 PM, Holger wrote:
>>>
>>> [...]
>>>
>>> The problem is that the message is consumed from the foo-queue and not
>>> rolled back within the transaction (the transaction seems to commit
>>> before
>>> sending the message to the bar-queue).
>>
>> Thanks,
>> Holger
>>
>> --
>> View this message in context:
>> http://camel.465427.n5.nabble.com/JMS-Transactions-not-handling-SecurityException-tp2256668p2259428.html
>> Sent from the Camel - Users mailing list archive at Nabble.com.
>>
>
>
>
> --
> Claus Ibsen
> Apache Camel Committer
>
> Author of Camel in Action: http://www.manning.com/ibsen/
> Open Source Integration: http://fusesource.com
> Blog: http://davsclaus.blogspot.com/
> Twitter: http://twitter.com/davsclaus
>
>
--
View this message in context:
http://camel.465427.n5.nabble.com/JMS-Transactions-not-handling-SecurityException-tp2256668p2259470.html
Sent from the Camel - Users mailing list archive at Nabble.com.
