openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Patrick Linskey" <plins...@bea.com>
Subject RE: JDBC SAvepointManager does not work
Date Tue, 16 Jan 2007 20:26:56 GMT
You'll also want to set ConnectionRetainMode to transaction, which will
ensure that OpenJPA has a single connection for the duration of the
transaction. Setting ConnectionRetainMode to transaction might also
automatically cause the connection to have autocommit disabled.

-Patrick

-- 
Patrick Linskey
BEA Systems, Inc. 

_______________________________________________________________________
Notice:  This email message, together with any attachments, may contain
information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated
entities,  that may be confidential,  proprietary,  copyrighted  and/or
legally privileged, and is intended solely for the use of the individual
or entity named in this message. If you are not the intended recipient,
and have received this message in error, please immediately return this
by email and then delete it. 

> -----Original Message-----
> From: Ritika Maheshwari [mailto:ritikamster@gmail.com] 
> Sent: Tuesday, January 16, 2007 12:05 PM
> To: open-jpa-dev@incubator.apache.org
> Subject: Re: JDBC SAvepointManager does not work
> 
> you were right by setting Savepoint after some persistence 
> operation seems
> to fix the problem
> thanks
> ritika
> 
> 
> On 1/16/07, Abe White <awhite@bea.com> wrote:
> >
> > Try performing a persistence operation (persisting an entity,
> > changing a persistent entity, deleting an entity, etc) 
> before setting
> > the savepoint.  It could just be a bug with empty savepoints in
> > optimistic transactions (which aren't too useful anyway).
> > 
> ______________________________________________________________
> _________
> > Notice:  This email message, together with any attachments, 
> may contain
> > information  of  BEA Systems,  Inc.,  its subsidiaries  and 
>  affiliated
> > entities,  that may be confidential,  proprietary,  
> copyrighted  and/or
> > legally privileged, and is intended solely for the use of 
> the individual
> > or entity named in this message. If you are not the 
> intended recipient,
> > and have received this message in error, please immediately 
> return this
> > by email and then delete it.
> >
> 

Mime
View raw message