On 9 Sep, Jason Dillon wrote:
>> > So, the first question is why does an MDB with NotSupported cause TX
>> > timeouts?
>>
>> Hiram is the one who did the transaction parts of the MDB, but I would
>> geuss this is what is going on: An MDB is ALWAYS transacted (the receipt
>> that is), the flags only determins under what TX context the bean is
>> invoked. This mean there will allways be a transaction going on under
>> the hood.
>
> Is that by design... that NotSupported still runs with a TX?
Yes, but remember. The receipt is under a transaction, but not the bean.
>
> I don't really have time to look into this more. I think that changing the
> MDB to use a non-xa cf with NotSupported works.... but I am not 100% on
> that. I hope that is the case at least =|
Thats true, it should work fine.
//Peter
>
>> > Second, why does a message get redelivered to my MDB, but does not have its
>> > getJMSRedelivered() set to true?
>>
>> That was fixed in JBossMQ during the time I implemented the Dead Letter
>> Queue handler, which was commited after the RH stuff. There is a change
>> note about it.
>
> Great. Thanks.
>
> --jason
>
>
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-development
--
Jobba hos oss: http://www.tim.se/weblab
------------------------------------------------------------
Peter Antman Technology in Media, Box 34105 100 26 Stockholm
Systems Architect WWW: http://www.tim.se
Email: [EMAIL PROTECTED] WWW: http://www.backsource.org
Phone: +46-(0)8-506 381 11 Mobile: 070-675 3942
------------------------------------------------------------
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
