Turn on TRACE logging for
You will be able to see where transactions
start and stop and which methods are invoked
Thanks for the suggestion; I'll try that.
I was able to find a workaround by creating a new method in my entity bean which called getMembers and returned a transformation of the data in a new form (Vector). Then I put a RequiresNew constraint on *that* method and everything went fine.
So it appears that the logic was acceptable as long as it didn't cross bean boundries as a CMR Collection.