executeUpdate not updating and no exception thrown

[debbie shifferd]

Using Oracle 8.1.7.4 db and Weblogic 8.1 server

It's one of those problems where I can't see anything wrong with the code, but its not updating the table and its not throwing an exception either.

Here's the code:

daoUtil.leaseSession();
 
String qryUpdateMDRequestHeader =
       "update md_request_hdr set auth_user_id=?, "+ 
       "auth_date=?, additional_instructions=?, pickup_instructions=?, req_pickup_date=? "+
       "where customer_id=? and "+
       "tracking_number=? ";
 
params = new DAOValue[7];
params[0] = DAOValueFactory.newValue(invo.getAuthId());
params[1] = DAOValueFactory.newValue(inputDt);  
params[2] = DAOValueFactory.newValue(invo.getAdditionInstr());
params[3] = DAOValueFactory.newValue(invo.getPickupInstr()); 
params[4] = DAOValueFactory.newValue(invo.getReqPickupDate()); 
params[5] = DAOValueFactory.newValue(invo.getCustomerId());
params[6] = DAOValueFactory.newValue(invo.getTRKNumber());      
 
rowsUpdated = daoUtil.executeSQL(qryUpdateMDRequestHeader, params);
 
 if(rowsUpdated < 1)
 {
     System.out.println("ERROR");
 }
 
===== executeSQL runs out of a DAOUtility class as follows
public int executeSQL(String query, DAOValue[] values)
      throws DatabaseException, ConnectionException
   {
      
      ed.setMethodName("executeSQL()");
      PreparedStatement prepStmt = null;
      int retValue = -1;
      String actval = "";
      leaseSession();
      try
      {
         
         prepStmt = getPreparedStatement(query);
         for (int i = 0; i < values.length; i++)
         {
            values[i].intsertValueIntoStatement(prepStmt, i + 1);
            actval = (values[i].isNull()) ? "Null" : values[i].toString();
            
         }
         retValue = prepStmt.executeUpdate();
         System.out.println("modified rows " + retValue);
      }
      catch (SQLException e)
      {
         ed.setTechMessage(e.getMessage());
         ed.setUserMessage("Data access error occured during SQL execution.");
         throw new DatabaseException(ed, e);
      }
      finally
      {
         releaseSession();
      }
      return retValue;
   }

==========
As I watch the flow of the code in the console log, I know the code executes:

rowsUpdated = daoUtil.executeSQL(qryUpdateMDRequestHeader, params);

Right before that line, I print out the query and the params:
qryUpdateMDRequestHeader = update md_request_hdr set auth_user_id=?, auth_date=?, additional_instructions=?, pickup_inst
ructions=?, req_pickup_date=? where customer_id=? and tracking_number=? params = v050754 09/04/2006 08:58:30 None None
09/11/2006 VzEast MD5127357

I had print lines in the executeSQl as well and know it was reaching there as well.

What I do not see is the executeSQL line " System.out.println("modified rows " + retValue);"

Nor do I ever see the "ERROR" line printout. I had also added a line to the finally of the executeSQL to print out rowsUpdated which equalled -1.

Yet the code keeps going, never throws an exception and continues the rest of the processing.

I've copied and pasted the sql into Golden32 (oracle sql program) and the query runs find with the params passed and updates the table.

Any thoughts at all as to either how I can troubleshoot this or what may be occurring?

[added code tags]
[ September 04, 2006: Message edited by: Jeanne Boyarsky ]

[Jeanne Boyarsky]

Debbie,
Can you confirm the value of rowsUpdated immediately before the statement:
if(rowsUpdated < 1)

Also, I don't see where rowsUpdated is declared? Can I assume it is an int?

[debbie shifferd]

In the beginning of the method rowsUpdated is defined as follows:

int rowsUpdated = -1;

[Scott Johnson]

If I had to guess, I'd say an Exception (other than SQLException) is being thrown inside the try clause before the println().

Add this code after catch(SQLException e) clause:

catch(Throwable e) 
{
   e.printStackTrace();
}

And run the program again.

Since you aren't catching the Exception, the Exception is passing up through the call stack until some other method catches it. This is why you don't see the ERROR and modified rows messages -- your methods don't get a chance to complete.
[ September 04, 2006: Message edited by: Scott Johnson ]