This is an old
thread, just wondering if anyone had the same problem with the transaction pool puzzle.
Read through the discussion on the other thread offered by Dale.
I had to disagree that the pool puzzle is in the same situation. Meaning, I don't see a nested transaction danger here.
For a nested transaction to happen, we've to have a method, with a pre-existing context, that calls another method that requires a new context, without the existing context being closed.
Here, none of the CMT bean's methods are invoking another method that requires a new context (at least we cannot tell from the information we've).
The second invocation of cmtRequiresNew() does not cause nested transactions to happen.