Thanks Justin for sharing the pain. I thought I was alone. I am very interested to see the source where you have duplicated this issue. I would like you to also include your ejb-jar.xml sections. If I can find the exact situation, I may be able to come up with a test case, a work around, or even delve into the JBoss code (the horror). This is a dead stop issue for my project at the moment so I am eager to see what you have.
>I am getting the very same error message in a very similar use case. The only >difference I can see is that all the methods of the offending bean are set to >'Required' rather than 'RequiresNew'. The error occurs when I try to call >the get methods of the bean through a local interface in a session bean. I >lookup the bean with the findByPrimaryKey method like you do, but in my case, >the record already exists in the DB. Perhaps this problem is not related to >the tx setting, since yours did not fail with RequiresNew in a simple case, >and mine fails with Required in my case? >I am in the process of creating a simple test for this problem. I'll post the >results here if/when I find out anything of potential use. _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
