Re: Unable to commit: transaction marked for rollback

David Kerr <dmk(at)mr-paradox(dot)net> wrote:

> Would postgres normally log the error in the TX?

A previous statement should have generated the original exception,
if that's what you mean.

> (it's not, which is why i'm asking)

Where are you checking? If you're talking about exceptions you're
fielding, it wouldn't be the first time I've seen sloppy exception
handling hide the first exception (the one that actually matters)
and throw a secondary exception. One common mistake is to catch the
first exception and try to do some cleanup, but allow an exception
to be thrown from the cleanup code -- completely hiding the first
exception.

The general pattern I follow to prevent such problems is:

ResourceX rx = null;
ResourceY ry = null;
try
{
rx = new ResourceX();
ry = rx.createY();
<use resources>
ry.close();
ry = null;
rx.close();
rx = null;
}
finally
{
if (ry != null)
{
try
{
ry.close();
}
catch (Exception e2)
{
// ignore
}
ry = null;
}
if (rx != null)
{
try
{
rx.close();
}
catch (Exception e2)
{
// ignore
}
rx = null;
}
}

There are, of course, variations on this, but you get the gist of
it.

Have you checked the PostgreSQL log file for clues? If you're not
seeing what you need, you could tweak the logging to show more.

-Kevin