CMP beans and Container Managed Transaction question - more information

2002-01-24 Thread Jeff Hubbach
More developments... With -Djdbc.debug=true, the failed transaction leaves a Dirty Connection around on both Oracle and PostgreSQL, so I guess the next question is... what constitutes a Dirty Connection? and is that's what's causing the lock? In further trials, we also tested updating that

Re: CMP beans and Container Managed Transaction question - more information

2002-01-24 Thread Romen Law
[EMAIL PROTECTED] Sent: Friday, January 25, 2002 9:17 AM Subject: CMP beans and Container Managed Transaction question - more information More developments... With -Djdbc.debug=true, the failed transaction leaves a Dirty Connection around on both Oracle and PostgreSQL, so I guess the next

CMP beans and Container Managed Transaction question

2002-01-22 Thread Jeff Hubbach
I'm hoping someone can give some insight as to why this is happening. I have a very simple test case with one stateless session bean and 2 CMP entity beans. The session bean just acts as a controller to modify the entity beans. All transactions are container-managed at the session bean. The