You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@openjpa.apache.org by ubiteck <su...@gmail.com> on 2012/06/05 10:10:15 UTC

PostgreSQL 9.1 [Error :current transaction is aborted]

I'm using *OpenJPA 2.1.1* with *Postgres 9.1*. My persistence.xml file
contains the following parameters :


	&lt;property name="openjpa.jdbc.SynchronizeMappings"
value="buildSchema(SchemaAction=add,ForeignKeys=true)" /&gt;
	&lt;property name="openjpa.ConnectionFactoryProperties"
value="PrettyPrint=true, PrettyPrintLineLength=200" /&gt;
	&lt;property name="openjpa.jdbc.DBDictionary"
value="postgres(SearchStringEscape=\)"/&gt;


I got a ReportingSQLException when JPA tries to get the name of a sequence
to define the identity of my entity bean.


*Exception stack trace*

2012-06-04 23:09:24,038 WARN  [JDBC] Unable to determine which sequences are
owned by the database. OpenJPA will consider all sequences suffixed with
"_seq" as database managed.  This may result in improper creation or removal
of sequences with this suffix. The original PostgreSQL driver exception is
being logged for your reference.
org.apache.openjpa.lib.jdbc.ReportingSQLException: ERROR: current
transaction is aborted, commands ignored until end of transaction block
{prepstmnt 155836080 
SELECT pg_get_serial_sequence(?, ?) 
[params=?, ?]} [code=0, state=25P02]
at
org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:281)
at
org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:257)
at
org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.access$1000(LoggingConnectionDecorator.java:72)
at
org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator$LoggingConnection$LoggingPreparedStatement.execute(LoggingConnectionDecorator.java:1295)
at
org.apache.openjpa.lib.jdbc.DelegatingPreparedStatement.execute(DelegatingPreparedStatement.java:386)
at
org.apache.openjpa.jdbc.sql.PostgresDictionary.queryOwnership(PostgresDictionary.java:467)
at
org.apache.openjpa.jdbc.sql.PostgresDictionary.isOwnedSequence(PostgresDictionary.java:441)
at
org.apache.openjpa.jdbc.sql.PostgresDictionary.isSystemSequence(PostgresDictionary.java:409)
at
org.apache.openjpa.jdbc.schema.SchemaGenerator.generateSequences(SchemaGenerator.java:960)
at
org.apache.openjpa.jdbc.schema.SchemaGenerator.generateSchema(SchemaGenerator.java:367)
at
org.apache.openjpa.jdbc.schema.SchemaGenerator.generateSchemas(SchemaGenerator.java:300)
at
org.apache.openjpa.jdbc.schema.SchemaTool.getDBSchemaGroup(SchemaTool.java:1163)
at org.apache.openjpa.jdbc.schema.SchemaTool.add(SchemaTool.java:363)
at org.apache.openjpa.jdbc.schema.SchemaTool.run(SchemaTool.java:340)
at org.apache.openjpa.jdbc.meta.MappingTool.record(MappingTool.java:505)
at org.apache.openjpa.jdbc.meta.MappingTool.record(MappingTool.java:456)
at
org.apache.openjpa.jdbc.kernel.JDBCBrokerFactory.synchronizeMappings(JDBCBrokerFactory.java:160)
at
org.apache.openjpa.jdbc.kernel.JDBCBrokerFactory.synchronizeMappings(JDBCBrokerFactory.java:164)
at
org.apache.openjpa.jdbc.kernel.JDBCBrokerFactory.newBrokerImpl(JDBCBrokerFactory.java:122)
at
org.apache.openjpa.kernel.AbstractBrokerFactory.newBroker(AbstractBrokerFactory.java:210)
at
org.apache.openjpa.kernel.DelegatingBrokerFactory.newBroker(DelegatingBrokerFactory.java:156)
at
org.apache.openjpa.persistence.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:227)
at
org.apache.openjpa.persistence.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:60)
at
org.apache.geronimo.persistence.CMPEntityManagerTxScoped.createEntityManager(CMPEntityManagerTxScoped.java:77)
at
org.apache.geronimo.persistence.CMPEntityManagerTxScoped.getEntityManager(CMPEntityManagerTxScoped.java:58)
at
org.apache.geronimo.persistence.CMPEntityManagerTxScoped.createNamedQuery(CMPEntityManagerTxScoped.java:419)
......


Thanks in advance

--
View this message in context: http://openjpa.208410.n2.nabble.com/PostgreSQL-9-1-Error-current-transaction-is-aborted-tp7580209.html
Sent from the OpenJPA Users mailing list archive at Nabble.com.

Re: Verified database matrix (was: PostgreSQL 9.1 [Error :current transaction is aborted])

Posted by ubiteck <su...@gmail.com>.
Kevin,
As recommended I created a JIRA  OPENJPA-2297
<https://issues.apache.org/jira/browse/OPENJPA-2297>  
I'm using PostgreSQL 8.4 with Geronimo 3.0, JDK 1.6 Sébastien



--
View this message in context: http://openjpa.208410.n2.nabble.com/PostgreSQL-9-1-Error-current-transaction-is-aborted-tp7580209p7581684.html
Sent from the OpenJPA Users mailing list archive at Nabble.com.

Re: Verified database matrix (was: PostgreSQL 9.1 [Error :current transaction is aborted])

Posted by Kevin Sutter <kw...@gmail.com>.
Hi sursini,
Excellent debug work!  I took a look at the code and you are right.  The
buildNames() method is using the underscore as the separator and causing
the issue.  Can you create a JIRA for this issue?  Thank you.

Just curious, what type of runtime environment are you using OpenJPA and
Postgres?  JSE?  App Server?  Which one?  Just a random survey...  :-)
Thanks!

Kevin

On Thu, Nov 8, 2012 at 3:56 AM, ubiteck <su...@gmail.com> wrote:

> I found the issue. The problem is related to the use of the underscore in
> table name. Let's imagine you have an entity called *SubscriptionEvent
> *with
> an auto generated field called *id* (/GenerationType.IDENTITY/).
> You want OpenJPA to create a table named SUBSCRIPTION_EVENT by using the
> following annotation to please you DBA with is favorite naming convention :
>    @Table(name="SUBSCRIPTION_EVENT")
> The problem occurs when the class PostgresDictionary try to determine
> whether a sequence is owned by the database using the method is
> /isOwnedSequence/. This method use another method called *buildNames* to
> define what is the table name and the column name to provide the parameters
> to the sql statement :
> SELECT pg_get_serial_sequence(?, ?)
> The argument provided to *buildNames* according to the name provided in the
> annotation @Table and the identity field is : "subscription_event_id".
> BuildNames split this string using the underscore as separator interpreting
> this :
> *   Table name : *      subscription
> *  Column name :*       event_id
>
> instead of
> *   Table name :*        subscription_event
> *Column name :* id
> As a workaround you have to remove the underscore in you table or field
> name. But it is in my opinion a bug to rely on the underscore to split the
> table from the column name.
>
>
>
>
> --
> View this message in context:
> http://openjpa.208410.n2.nabble.com/PostgreSQL-9-1-Error-current-transaction-is-aborted-tp7580209p7581664.html
> Sent from the OpenJPA Users mailing list archive at Nabble.com.

Re: Verified database matrix (was: PostgreSQL 9.1 [Error :current transaction is aborted])

Posted by ubiteck <su...@gmail.com>.
I found the issue. The problem is related to the use of the underscore in
table name. Let's imagine you have an entity called *SubscriptionEvent *with
an auto generated field called *id* (/GenerationType.IDENTITY/). 
You want OpenJPA to create a table named SUBSCRIPTION_EVENT by using the
following annotation to please you DBA with is favorite naming convention :  
   @Table(name="SUBSCRIPTION_EVENT") 
The problem occurs when the class PostgresDictionary try to determine
whether a sequence is owned by the database using the method is
/isOwnedSequence/. This method use another method called *buildNames* to
define what is the table name and the column name to provide the parameters
to the sql statement : 
SELECT pg_get_serial_sequence(?, ?) 
The argument provided to *buildNames* according to the name provided in the
annotation @Table and the identity field is : "subscription_event_id".
BuildNames split this string using the underscore as separator interpreting
this :
*   Table name : *	subscription 
*  Column name :*	event_id

instead of 
*   Table name :*	 subscription_event 
*Column name :*	id
As a workaround you have to remove the underscore in you table or field
name. But it is in my opinion a bug to rely on the underscore to split the
table from the column name.   
  



--
View this message in context: http://openjpa.208410.n2.nabble.com/PostgreSQL-9-1-Error-current-transaction-is-aborted-tp7580209p7581664.html
Sent from the OpenJPA Users mailing list archive at Nabble.com.

Re: Verified database matrix (was: PostgreSQL 9.1 [Error :current transaction is aborted])

Posted by Kevin Sutter <kw...@gmail.com>.
Hi Fredrik,
Good to know that Postgres v9.0 and v9.1 are working for you.  The OpenJPA
documentation could very well be out of date.  But, we do rely on
volunteers to perform testing and verification of the various database
versions.  Especially with the open-source database variations.

Due to the recent questions regarding Postgres on the mailing lists, I did
reach out to the developer that used to "maintain" the Postgres
DBDictionary.  Unfortunately, he has some new responsibilities and will not
be able to perform the verification that he used to perform for Postgres.
So, we are looking for a new volunteer...

OpenJPA has a large suite of JUnits.  By default, the test bucket is run
with Derby, but it is easily configurable to run with other databases.  If
anybody has the bandwidth to run the JUnit bucket against newer versions of
Postgres and follow-up with any incompatibilities, it would be greatly
appreciated!  And, then maybe we can get the documentation up-to-date...
:-)

Thanks,
Kevin

On Sun, Jun 10, 2012 at 5:04 AM, Fredrik Jonson <fr...@jonson.org> wrote:

> Kevin Sutter wrote:
>
> >  It looks like OpenJPA has only been tested with v8.4.
> >
> http://openjpa.apache.org/builds/latest/docs/docbook/manual.html#dbsupport
>
> Wonder if that's not mostly a sign that this section of the docs is
> outdated?
>
> Otherwise: what is the procedure for getting a not-so-ancient verison of
> postgresql on to that list? Since 8.4, we've seen 9.0 released in 2010,
> and 9.1
> released in 2011. I've used postgresql 9.0 and 9.1 with openjpa, and apart
> from issue 2056 I haven't found any obvious incompatibilities.
>
> https://issues.apache.org/jira/browse/OPENJPA-2056
>
> --
> Fredrik Jonson
>
>

Verified database matrix (was: PostgreSQL 9.1 [Error :current transaction is aborted])

Posted by Fredrik Jonson <fr...@jonson.org>.
Kevin Sutter wrote:

>  It looks like OpenJPA has only been tested with v8.4.
>  http://openjpa.apache.org/builds/latest/docs/docbook/manual.html#dbsupport

Wonder if that's not mostly a sign that this section of the docs is outdated?

Otherwise: what is the procedure for getting a not-so-ancient verison of
postgresql on to that list? Since 8.4, we've seen 9.0 released in 2010, and 9.1
released in 2011. I've used postgresql 9.0 and 9.1 with openjpa, and apart
from issue 2056 I haven't found any obvious incompatibilities.

https://issues.apache.org/jira/browse/OPENJPA-2056

--
Fredrik Jonson

Re: PostgreSQL 9.1 [Error :current transaction is aborted]

Posted by Kevin Sutter <kw...@gmail.com>.
And, what is the output when you use the printParameters attribute on the
ConnectionFactoryProperties property?

Kevin

On Thu, Jun 7, 2012 at 3:13 AM, ubiteck <su...@gmail.com> wrote:

> There is no dumb question when you try to solve issues.
>
> *Database creation *
> I created the database the same way for both version (8.4 and 9.1) using
> the
> following commands :
>
> > sudo -i -u postgres
> > psql
> > CREATE USER admin;
> > ALTER ROLE admin WITH CREATEDB;
> > CREATE DATABASE sampleDB OWNER admin;
> > ALTER USER admin WITH ENCRYPTED PASSWORD 'mypassword';
>
> About the credentials. I executed successfully the incriminated stored
> procedure using the datasource configured in my Geronimo Server using the
> same credentials for both old (8.4) and new (9.1). I used the same
> credential (admin) using psql command line and the Geronimo datasource. In
> geronimo, you can use the administration console to execute sql using the
> credential defined in the datasource.
>
> I'm pretty confident to exclude the credentials assumption.
>
>
> *Same Database ? *
>
> I created the datasource the same way using the same database name.
>
> *Entity definition*
>
> Identity generation type :
>
> In my entity i'm defining my id using the following snippet :
>
>
>        /**
>         * @return the id
>         */
>        @Id
>        @GeneratedValue (strategy=GenerationType.IDENTITY)
>        public Long getId() {
>                return id;
>        }
>
> --
> View this message in context:
> http://openjpa.208410.n2.nabble.com/PostgreSQL-9-1-Error-current-transaction-is-aborted-tp7580209p7580230.html
> Sent from the OpenJPA Users mailing list archive at Nabble.com.
>

Re: PostgreSQL 9.1 [Error :current transaction is aborted]

Posted by ubiteck <su...@gmail.com>.
There is no dumb question when you try to solve issues. 

*Database creation *
I created the database the same way for both version (8.4 and 9.1) using the
following commands : 

> sudo -i -u postgres
> psql
> CREATE USER admin;
> ALTER ROLE admin WITH CREATEDB;
> CREATE DATABASE sampleDB OWNER admin;
> ALTER USER admin WITH ENCRYPTED PASSWORD 'mypassword';

About the credentials. I executed successfully the incriminated stored
procedure using the datasource configured in my Geronimo Server using the
same credentials for both old (8.4) and new (9.1). I used the same
credential (admin) using psql command line and the Geronimo datasource. In
geronimo, you can use the administration console to execute sql using the
credential defined in the datasource.

I'm pretty confident to exclude the credentials assumption.


*Same Database ? *

I created the datasource the same way using the same database name. 

*Entity definition*

Identity generation type :

In my entity i'm defining my id using the following snippet :


	/**
	 * @return the id
	 */
	@Id
	@GeneratedValue (strategy=GenerationType.IDENTITY)
	public Long getId() {
		return id;
	}

--
View this message in context: http://openjpa.208410.n2.nabble.com/PostgreSQL-9-1-Error-current-transaction-is-aborted-tp7580209p7580230.html
Sent from the OpenJPA Users mailing list archive at Nabble.com.

Re: PostgreSQL 9.1 [Error :current transaction is aborted]

Posted by Kevin Sutter <kw...@gmail.com>.
Right.  So, the use of the printParameters attribute would verify that the
invocation from within the JPA runtime matches what you are executing from
the command line...  And, if these two invocations are exactly the same,
but the command line works and the JPA runtime fails, then I would consider
the credentials used to connect to the database.  When you are running from
the command line, what credentials are used to connect to the database?
And, when you are defining your datasource for JPA, what credentials are in
use?  Another item to verify is whether you are connecting to the same
database...  I know it's a dumb question, but if this is working from the
command line, then we need to figure out what the difference is.

Good luck,
Kevin

On Wed, Jun 6, 2012 at 9:43 AM, ubiteck <su...@gmail.com> wrote:

> 1) I wasn't clear. I tried to execute the SQL sentence using psql
> (PostgreSQL
> interactive terminal) and it returns the name of the sequence without
> errors.
>
> --
> View this message in context:
> http://openjpa.208410.n2.nabble.com/PostgreSQL-9-1-Error-current-transaction-is-aborted-tp7580209p7580224.html
> Sent from the OpenJPA Users mailing list archive at Nabble.com.
>

Re: PostgreSQL 9.1 [Error :current transaction is aborted]

Posted by ubiteck <su...@gmail.com>.
1) I wasn't clear. I tried to execute the SQL sentence using psql (PostgreSQL
interactive terminal) and it returns the name of the sequence without
errors.  

--
View this message in context: http://openjpa.208410.n2.nabble.com/PostgreSQL-9-1-Error-current-transaction-is-aborted-tp7580209p7580224.html
Sent from the OpenJPA Users mailing list archive at Nabble.com.

Re: PostgreSQL 9.1 [Error :current transaction is aborted]

Posted by Kevin Sutter <kw...@gmail.com>.
Hi Sebastien,
1)  What do you mean it runs without problems?  You still get the exception
right?  What I was interested in were the actual parameter values being
passed in on the "select pg_get_serial_sequence" invocation.  I thought it
might shed some light on why this call wasn't working for you.

2)  Thanks for trying the alternate buildSchema configuration.

3)  Hmmm...  Postgres 8.4 works, huh?  Postgres must have changed something
in the area of sequences that is affecting our runtime.  Thanks for the
debugging efforts.  This may require a change in the Postgres DBDictionary
to allow support for Postgres 9.1.  I also noticed this JIRA (
https://issues.apache.org/jira/browse/OPENJPA-2196) which indicates some
other issue with Sequences and Postgres 9.1.

Kevin

On Wed, Jun 6, 2012 at 7:03 AM, ubiteck <su...@gmail.com> wrote:

> He Kevin,
> Thanks for your quick reply.
>
> 1) I added the printParameters attribute in my ConnectionFactory property
> to
> test the/ pg_get_serial_sequence/ stored procedure with the parameters
> displayed in the log. It runs without problems.
> 2) I tried to remove the SchemaAction parameters but it has no effects.
> 3) I downgraded Postgress to v8.4 on my ubuntu box to verify and it
> "solves"
> the problem.
>
> I will install the 9.1 version on my Mac and try to debug it.
>
> Sébastien
>
>
>
>
> --
> View this message in context:
> http://openjpa.208410.n2.nabble.com/PostgreSQL-9-1-Error-current-transaction-is-aborted-tp7580209p7580217.html
> Sent from the OpenJPA Users mailing list archive at Nabble.com.
>

Re: PostgreSQL 9.1 [Error :current transaction is aborted]

Posted by ubiteck <su...@gmail.com>.
He Kevin,
Thanks for your quick reply. 

1) I added the printParameters attribute in my ConnectionFactory property to
test the/ pg_get_serial_sequence/ stored procedure with the parameters
displayed in the log. It runs without problems. 
2) I tried to remove the SchemaAction parameters but it has no effects.
3) I downgraded Postgress to v8.4 on my ubuntu box to verify and it "solves"
the problem.

I will install the 9.1 version on my Mac and try to debug it.

Sébastien




--
View this message in context: http://openjpa.208410.n2.nabble.com/PostgreSQL-9-1-Error-current-transaction-is-aborted-tp7580209p7580217.html
Sent from the OpenJPA Users mailing list archive at Nabble.com.

Re: PostgreSQL 9.1 [Error :current transaction is aborted]

Posted by Kevin Sutter <kw...@gmail.com>.
Hi,
No easy answers, but a few things to check on...

o  I'm not an expert with Postgres, but it looks like OpenJPA has only been
tested with v8.4 [1].  I can't imagine that v9.1 introduced a problem in
this area, but it's something to be aware of.  Has this scenario worked in
the past on any previous versions of Postgres and/or OpenJPA?

o  There seems to be an issue with accessing the sequence as defined for
Postgres.  How are you defining the Sequence in your Entity and/or orm.xml?

o  Outputting the actual parameters to the SELECT pg_get_serial_sequence(?,
?) statement may be helpful since it will show the users and ids that are
being queried against.  You can turn on this option by adding
PrintParameters=True to the ConnectionFactoryProperties property.

o  For giggles, you could also remove the SchemaAction=add property.  By
default, the buildSchema will attempt to synchronize between the object
model and the database.  I'm not sure if the SchemaAction=add action is
causing the Postgres dictionary to take a slightly different path.  Worth a
shot anyway.

Good luck,
Kevin

[1]
http://openjpa.apache.org/builds/latest/docs/docbook/manual.html#dbsupport

On Tue, Jun 5, 2012 at 3:10 AM, ubiteck <su...@gmail.com> wrote:

> I'm using *OpenJPA 2.1.1* with *Postgres 9.1*. My persistence.xml file
> contains the following parameters :
>
>
>        &lt;property name="openjpa.jdbc.SynchronizeMappings"
> value="buildSchema(SchemaAction=add,ForeignKeys=true)" /&gt;
>        &lt;property name="openjpa.ConnectionFactoryProperties"
> value="PrettyPrint=true, PrettyPrintLineLength=200" /&gt;
>        &lt;property name="openjpa.jdbc.DBDictionary"
> value="postgres(SearchStringEscape=\)"/&gt;
>
>
> I got a ReportingSQLException when JPA tries to get the name of a sequence
> to define the identity of my entity bean.
>
>
> *Exception stack trace*
>
> 2012-06-04 23:09:24,038 WARN  [JDBC] Unable to determine which sequences
> are
> owned by the database. OpenJPA will consider all sequences suffixed with
> "_seq" as database managed.  This may result in improper creation or
> removal
> of sequences with this suffix. The original PostgreSQL driver exception is
> being logged for your reference.
> org.apache.openjpa.lib.jdbc.ReportingSQLException: ERROR: current
> transaction is aborted, commands ignored until end of transaction block
> {prepstmnt 155836080
> SELECT pg_get_serial_sequence(?, ?)
> [params=?, ?]} [code=0, state=25P02]
> at
>
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:281)
> at
>
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:257)
> at
>
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.access$1000(LoggingConnectionDecorator.java:72)
> at
>
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator$LoggingConnection$LoggingPreparedStatement.execute(LoggingConnectionDecorator.java:1295)
> at
>
> org.apache.openjpa.lib.jdbc.DelegatingPreparedStatement.execute(DelegatingPreparedStatement.java:386)
> at
>
> org.apache.openjpa.jdbc.sql.PostgresDictionary.queryOwnership(PostgresDictionary.java:467)
> at
>
> org.apache.openjpa.jdbc.sql.PostgresDictionary.isOwnedSequence(PostgresDictionary.java:441)
> at
>
> org.apache.openjpa.jdbc.sql.PostgresDictionary.isSystemSequence(PostgresDictionary.java:409)
> at
>
> org.apache.openjpa.jdbc.schema.SchemaGenerator.generateSequences(SchemaGenerator.java:960)
> at
>
> org.apache.openjpa.jdbc.schema.SchemaGenerator.generateSchema(SchemaGenerator.java:367)
> at
>
> org.apache.openjpa.jdbc.schema.SchemaGenerator.generateSchemas(SchemaGenerator.java:300)
> at
>
> org.apache.openjpa.jdbc.schema.SchemaTool.getDBSchemaGroup(SchemaTool.java:1163)
> at org.apache.openjpa.jdbc.schema.SchemaTool.add(SchemaTool.java:363)
> at org.apache.openjpa.jdbc.schema.SchemaTool.run(SchemaTool.java:340)
> at org.apache.openjpa.jdbc.meta.MappingTool.record(MappingTool.java:505)
> at org.apache.openjpa.jdbc.meta.MappingTool.record(MappingTool.java:456)
> at
>
> org.apache.openjpa.jdbc.kernel.JDBCBrokerFactory.synchronizeMappings(JDBCBrokerFactory.java:160)
> at
>
> org.apache.openjpa.jdbc.kernel.JDBCBrokerFactory.synchronizeMappings(JDBCBrokerFactory.java:164)
> at
>
> org.apache.openjpa.jdbc.kernel.JDBCBrokerFactory.newBrokerImpl(JDBCBrokerFactory.java:122)
> at
>
> org.apache.openjpa.kernel.AbstractBrokerFactory.newBroker(AbstractBrokerFactory.java:210)
> at
>
> org.apache.openjpa.kernel.DelegatingBrokerFactory.newBroker(DelegatingBrokerFactory.java:156)
> at
>
> org.apache.openjpa.persistence.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:227)
> at
>
> org.apache.openjpa.persistence.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:60)
> at
>
> org.apache.geronimo.persistence.CMPEntityManagerTxScoped.createEntityManager(CMPEntityManagerTxScoped.java:77)
> at
>
> org.apache.geronimo.persistence.CMPEntityManagerTxScoped.getEntityManager(CMPEntityManagerTxScoped.java:58)
> at
>
> org.apache.geronimo.persistence.CMPEntityManagerTxScoped.createNamedQuery(CMPEntityManagerTxScoped.java:419)
> ......
>
>
> Thanks in advance
>
> --
> View this message in context:
> http://openjpa.208410.n2.nabble.com/PostgreSQL-9-1-Error-current-transaction-is-aborted-tp7580209.html
> Sent from the OpenJPA Users mailing list archive at Nabble.com.