Big transaction problem...

Question

I have a big application to change, and my problem is in the connction:
I have to do it transactional so I can rollback all if fails... but the application fails and I don't know why.
When it should do a update in a table in which another inserts have been done previously -and many operations too in the same ddbb- it crash: there's no exception, the application is like waiting something...
I have only one static connection with the autocommit setted to false and the sqls are well done.
help pleaseeee Any idea?

Answer 1

It sounds like a tranaction is waiting on another. Based on your SQL server the esiest thing to do is to monitor the SQL server for Locked processes. A process will fire and tell you that it's waiting on another process to finish. Checkout the SQL executing in the locked process and try an tie this back to a SQL Statement within code.
You might find that you are writting into a recordset that's locked somewhere else. This will always timeout as one is waiting on the other :)
I think that Java 's default is to never time out the system will wait forever and not produce an exception but you can try and change this in your Database Handler class.
     public ResultSet getArray(String sql) throws SQLException {
          Statement stmt = this.con.createStatement(ResultSet.TYPE_SCROLL_INSENSITIVE, ResultSet.CONCUR_READ_ONLY);
          stmt.setQueryTimeout(3);
          try {
          ResultSet rs = stmt.executeQuery(sql);
          return rs;
          } catch(SQLException e) {
               // Break here and find out whats goin on!
               system.out.println("SQL Crapped out: " + sql);
          return null;
     }You can then wait for the timeout and catch the SQLException
Edited by: Gizard on Apr 21, 2009 6:01 AM