openjpa-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marco de Booij <mdeb...@scarlet.be>
Subject Re: Postgres sequence: current transaction is aborted
Date Mon, 18 Jun 2012 20:17:01 GMT
I searched further. Somebody mentioned to add allocationSize=1 to the 
@SequenceGenerator but this did not solve the problem. I now get a 
simple alter sequence statement that looks like the problem 
(OPENJPA-2196) Create Sequence Postgres 9.1. Hope that this helps you a 
bit more.

2012-06-18 22:16:18 CEST LOG:  execute S_2: COMMIT
2012-06-18 22:16:18 CEST LOG:  execute S_1: BEGIN
2012-06-18 22:16:18 CEST ERROR:  syntax error at end of input at 
character 35
2012-06-18 22:16:18 CEST STATEMENT:  ALTER SEQUENCE DOOS.SEQ_I18N_CODES
2012-06-18 22:16:18 CEST ERROR:  current transaction is aborted, 
commands ignored until end of transaction block
2012-06-18 22:16:18 CEST STATEMENT:  SELECT NEXTVAL('DOOS.SEQ_I18N_CODES')
2012-06-18 22:16:18 CEST LOG:  execute S_3: ROLLBACK

Regards,

Marco

Op 18-06-12 15:28, Kevin Sutter schreef:
> Hi Marco,
> That 25P02 state from Postgres is so nebulous...  It really doesn't help
> explain the problem that Postgres is complaining about...  We've had some
> recent activity on the OpenJPA mailing lists related to Postgres and
> Sequences.  It seems that we have varying degrees of success with different
> customers.
>
> Can you post the complete stack when you receive this error?  Have you
> searched the log for other problems leading up to this Error?  Have you
> tried turning on Trace for both OpenJPA and Postgres?  No guarantees, but
> Trace might shed some light on the issue.
>
> The Junit bucket for OpenJPA has various tests relating to Id generation
> and sequences, and these seem to work with Postgres...  So, we might need
> some assistance with narrowing in the test and debug setup to help
> reproduce the problem and eventually solve it.
>
> Thanks,
> Kevin
>


Mime
View raw message