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 <surs...@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. >
