Uncable to commit: transaction marked for rollback

On 7/1/2010 11:10 AM, Tom Lane wrote:

David Kerr<dmk@mr-paradox.net> writes:

I'm intermittantly getting this error message in a java app.
using Geronimo / Hibernate / Postgres 8.3.9

javax.transaction.RollbackException: Unable to commit: transaction marked for
rollback

You might have better luck asking about that on pgsql-jdbc --- there's
no such error condition in Postgres proper, so it must be coming from
somewhere on the Java side.

regards, tom lane

Ok - thanks!

Dave

David Kerr <dmk@mr-paradox.net> writes:

I'm intermittantly getting this error message in a java app.
using Geronimo / Hibernate / Postgres 8.3.9

javax.transaction.RollbackException: Unable to commit: transaction marked for
rollback

You might have better luck asking about that on pgsql-jdbc --- there's
no such error condition in Postgres proper, so it must be coming from
somewhere on the Java side.

regards, tom lane

Hi,

it happens fi at transaction timeout or you executed a broken/failed
statement und catched the exception

try { call invalid sql } catch (Exception e) {}
connection.commit() <- exception throws here, happens automatically
inside your appserver

regards
Thomas

Am 01.07.2010 20:06, schrieb David Kerr:

On 2010-07-01, David Kerr wrote:

I'm intermittantly getting this error message in a java app.
using Geronimo / Hibernate / Postgres 8.3.9

javax.transaction.RollbackException: Unable to commit:
transaction marked for
rollback

Can someone give me a scenario where this would happen?
"unable to commit"
makes everyone immediatly go to database issue. But it seems
like an app
issue to me.

I was thinking that maybe it's a 2 phase commit / XA or
something like that.
(TX open, phase 1 commit fails, phase 2 commit throws this error?)

I can't imagine how this would happen within a single
transaction setup.

Thanks!

Dave

-- Sent via pgsql-general mailing list (pgsql-general@postgresql.org)

To

make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

Hallo,
as Tom Lane already pointed out, the issue is definitely on the Java
side if you cannot find any PSQLException related to it.

The exception is generated by the Java Transaction Api. May be an EJB
failed could was not available during the transaction or threw an
exception.

--
Robert...