Resultset Exhausted

[Rahul Juneja]

Hi guys,

Was just wondering if anybody could suggest anything as I am getting a resultset Exhausted exception and my query returned 1 record when directly executed thru oracle client.

   
 
        ResultSet rs = pstmt.executeQuery();
        try {
          rs.next();
          retValue = createNew(rs);
        }
        finally {
          rs.close();
        }
      }
      finally {
        pstmt.close();
      }
      return retValue;
    }
    catch (SQLException e) {
      logger.error("" + ErrorCode.DB_LOAD_V_CLOSE_INFO, e);
      throw new DatabaseException(ErrorCode.DB_LOAD_V_CLOSE_INFO, e);
    }
    finally {
      if (logger.isDebugEnabled()) {
        logger.debug("load() ->" + retValue);
      }
    }
 
 
 
 
 
 
 
 
public VCloseInfoPLC createNew(ResultSet rs) throws DatabaseException {
    if (logger.isDebugEnabled()) {
      logger.debug("createNew(" + rs + ")<-");
    }
    VCloseInfoPLC retValue = createNew();
    try {
      retValue.transID = new Long(rs.getLong("TRANSID")); 
 

[ July 13, 2005: Message edited by: Rahul Juneja ]

[Jeanne Boyarsky]

Rahul,
Try printing out the value of rs.next(). If it displays false, as I suspect it does, there are no [more] rows and you are calling rs.getLong() on an invalid row.

[Rahul Juneja]

Thanks dude but i found the problem.

[Sonny Gill]

Originally posted by Rahul Juneja:
Thanks dude but i found the problem.

And the problem was...

[Rahul Juneja]

Actually, I was using a seperate thread for committing certain process and again trying to access the commited data from the main thread, so sometimes the thread used for committing data is not yet finished and the main thread tries to access that data.


Okay, If you can answer my this question as When we call commit on a transaction context which has lot of changes done and all are to be commited will the control be given to a seperate database thread automatically.

Cheeers,
Rahul