RE: [JBoss-user] Weblogic to JBoss Migration - Differences in XA and Non-XA DataS ource handling (Stack Trace)

2003-11-19 Thread Yates, Danny
PROTECTED] Subject: Re: [JBoss-user] Weblogic to JBoss Migration - Differences in XA and Non-XA DataS ource handling (Stack Trace) Sasidharan, Manoj wrote: > Yes. But I am trying to do this on a Non-XA datasource connection. This > should in no way impact the on-going user transaction. I

RE: [JBoss-user] Weblogic to JBoss Migration - Differences in XA and Non-XA DataS ource handling (Stack Trace)

2003-11-18 Thread Sasidharan, Manoj
TECTED] > Sent: Tuesday, November 18, 2003 4:50 AM > To: [EMAIL PROTECTED] > Subject: Re: [JBoss-user] Weblogic to JBoss Migration - Differences in > XA and Non-XA DataS ource handling (Stack Trace) > > > Are you trying to set autocommit? You can not do it in a managed

Re: [JBoss-user] Weblogic to JBoss Migration - Differences in XA and Non-XA DataS ource handling (Stack Trace)

2003-11-18 Thread Alexey Loubyansky
-user] Weblogic to JBoss Migration - Differences in XA and Non-XA DataS ource handling (Stack Trace) Are you trying to set autocommit? You can not do it in a managed tx. Sasidharan, Manoj wrote: Hello Adrian, Thanks for taking some time for helping me on this issue. Here is the stack trace at the

RE: [JBoss-user] Weblogic to JBoss Migration - Differences in XA and Non-XA DataS ource handling (Stack Trace)

2003-11-18 Thread Sasidharan, Manoj
- From: Alexey Loubyansky [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 18, 2003 4:50 AM To: [EMAIL PROTECTED] Subject: Re: [JBoss-user] Weblogic to JBoss Migration - Differences in XA and Non-XA DataS ource handling (Stack Trace) Are you trying to set autocommit? You can not do it in a managed tx

Re: [JBoss-user] Weblogic to JBoss Migration - Differences in XA and Non-XA DataS ource handling (Stack Trace)

2003-11-18 Thread Alexey Loubyansky
Are you trying to set autocommit? You can not do it in a managed tx. Sasidharan, Manoj wrote: Hello Adrian, Thanks for taking some time for helping me on this issue. Here is the stack trace at the server when the problem occurs. 20:26:31,122 WARN [TxConnectionManager$LocalXAResource] Prepare ca