openjpa-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kevin Sutter <kwsut...@gmail.com>
Subject Re: PostgreSQL 9.1 [Error :current transaction is aborted]
Date Thu, 07 Jun 2012 16:09:29 GMT
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 <sursini@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.
>

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