Yes, it seems to be. We have had no problems with rollback since. But I am concerned about using ConnectionFactoryPooledImpl with Weblogic and a data source. The comments in ojb.properties seem to imply that I should only be using ConnectionFactoryManagedImpl. And thinking about it, I am concerned about the implications of using OJB pooling on top of Weblogic connection pooling.
thanks, Bonnie MacKellar > -----Original Message----- > From: Armin Waibel [mailto:[EMAIL PROTECTED] > Sent: Tuesday, October 07, 2003 8:16 PM > To: OJB Users List > Subject: Re: rollback problem > > > Hi Bonnie, > > is this problem solved by > setting > > useAutoCommit="1" > as you posted in an later mail? > > regards, > Armin > > On Thu, 2 Oct 2003 15:54:28 -0400, Bonnie MacKellar > <[EMAIL PROTECTED]> > wrote: > > > > > Hi, > > > > I have a simple two step transaction, in which two inserts > occur. I am > > using > > PB broker, with OJB transactions. I am connecting to a data > source in > > Weblogic. I am using rc4. > > > > When a rollback occurs, the first record inserted in the > transaction is > > not > > removed. This is very incorrect, of course. I looked back > in the archives > > for this list, and found a message saying not to use > > ConnectionFactoryManagedImpl if you are using OJB > transactions. Fine. So > > I > > switched to ConnectionFactoryPooledImpl. But the problem > remains. Is > > there a > > known problem with this? > > > > My code is > > try > > { > > broker.beginTransaction(); > > > > broker.store(customer); > > broker.store(audit); > > > > broker.commitTransaction(); > > > > } > > catch (Exception e) > > { > > broker.abortTransaction(); > > logger.error(e.getMessage()); > > } > > } > > > > I am attaching my ojb.properties as well. > > > > Thanks, > > Bonnie MacKellar > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
