Hi,
Just my US$0.02:
If you need more verbose debug-level logging
to see what is happening with transactions,
try changing the constant
static private final boolean trace = false;
near the top of org/jboss/tm/TxCapsule.java.
Toby Allsopp wrote:
> I have a BMT SFSB, call it SFBean, that starts a transaction in method
> a() and then calls a method on a CMT SLSB, call it SLBean.a().
> SFBean.a() returns without completing the transaction. The client then
> calls SLBean.b(), which is marked as Required, and JBoss complains that
> there is already a transaction active and it can't nest the new one.
>
> 1. Client calls SFBean.a()
> 2. SFBean.a() starts a transaction
> 3. SFBean.a() calls SLBean.a()
> 4. SLBean.a() returns
> 5. SFBean.a() returns
Here, the BMT interceptor ought to
disassociate the bean transaction from the
current thread.
If this does not happen, and the client is
in the same VM, I guess that the SLBean.b()
call will have this transaction still
associated.
Best Regards,
Ole Husgaard.
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
List Help?: [EMAIL PROTECTED]
