openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kevin Sutter <>
Subject Re: Savepoint issue with OpenJPA
Date Tue, 30 Oct 2012 13:11:32 GMT
I'm going to cross-post to the Users forum since you may find some users of
the Savepoint feature out there...  Savepoints are not what I would call a
"mainline" feature.  Yes, they have been part of the OpenJPA project since
day one, but I have not heard of too many actual customer scenarios using
this feature.  Hopefully, you'll get some hits from the Users forum...
Good luck!


On Mon, Oct 29, 2012 at 9:19 PM, pankajpriyadarshi <>wrote:

> Hello, I am using the Savepoint feature of OpenJPA (setSavepoint and
> rollbackToSavepoint). When I do a rollbackToSavepoint the order of the
> TransactionalObjects becomes random. E.g. If the rollbackToSavepoint call
> is
> not made, the insertions are made in the order of the operation: 1) Insert
> Record 1 into ParentTable 2) Insert Record 1.1 into ChildTable 3) Insert
> Record 1.2 into ChildTable 4) Insert Record 1.3 into ChildTable 5) Insert
> Record 2 into ParentTable 6) Insert Record 2.1 into ChildTable 7) Insert
> Record 2.2 into ChildTable 8) Insert Record 2.3 into ChildTable If the
> rollbackToSavepoint call is made, the insertions order becomes random and I
> am getting foreign key constraint violations. I have tried to set
> openjpa.jdbc.UpdateManager to operation order but it has no affect. Is
> there
> any way I can preserve the original order of the operation. Why would
> OpenJPA try to reorder the transactional objects when doing a
> rollbackToSavepoint . Has someone faced this issue before. OpenJPA version
> info:revision.number=422266:1141200 openjpa.version=2.1.1-SNAPSHOT
> openjpa.enhancer.revision=1055128 Thank You, Pankaj Priyadarshi
> --
> View this message in context:
> Sent from the OpenJPA Developers mailing list archive at

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message