On 22 May 00, at 10:07, Rickard �berg wrote:
>
> > So other than confirming the sequence above, I have one major
> > question left. The only place we can run into trouble (that is, a
> > connection isn't committed or rolled back or released to the pool for a
> > long period of time - say, 20+ minutes) is when the clients or beans
> > manage their own transactions (is this distinct from bean-managed
> > persistance?).
>
> We can detect this case actually. If a bean should manage its own
> transactions, and a method is called that has no tx associated with it,
> but one is running on return, we can know that it hasn't ended the tx
> properly and can thus complain. So tx's will always be closed properly
> regardless of mode (container mgd, or bean mgd).
>
Hi Rickard,
If I understand what you are saying I don't think this is true. A
client using UserTransaction can actually keep a transaction open
between business method calls. This is a terrible practice from a
resource-usage standpoint, but specifically allowed in the spec for
the case of stateful session beans.
-Dan
