> > > 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?
>
The reason you have tx running is cause when you use a XAConnectionFactory,
sessions are allways transacted. What happens with a NotSupported, is that
the transaction that the message came in with will be dissasociated from the
thread before we call the onMessage method. After the onMessage returns,
the original transaction is commited ( to do the message acknowlegment. )
>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 =|
>
What's going on thats giving you all this grief???
Regards, Hiram
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
