1 Reply Latest reply on Nov 19, 2002 9:39 AM by Dave

    Why are transactions held open?

    Dave Newbie

      I have a problem with my Postgres database ... The new feature in Postgres 7.2 that allows the database to be VACUUMed without locking the tables does not seem to work for me. I posted to the Postgres list and was told that the reason it wasn't working was due to the fact that all of my connections from JBOSS were "idle in transaction" ... Sure enough, by setting Postgres into DEBUG mode, I can see that when JBOSS connects to the database, it somehow starts a transaction (I see the BEGIN issued to the postgres backend) ...

      I tested with a standalone JDBC application and this behavior is not exhibted (even after running setAutoCommit(false)) ...

      The question is: Why does JBOSS do this? and Is there a way to stop this behavior?

      This is a significant problem for my application now that the tables are geting quite large ... We currently use the VACUUM FULL and the exlusive locks on some of the tables are stopping certain business applications from running ...

      Thanks in advance,
      Dave