java.sql.SQLException... Need help!!!

[George Larry]

I have a page that works just fine... I make numerous calls to the db with no problems... until- I try to run this report.
It looks something like this:

cs = con.prepareCall ( "{ call selectDept ( ? ) }" );
cs.registerOutParameter( 1, oracle.jdbc.driver.OracleTypes.CURSOR );
cs.execute();
rs = ( ResultSet ) cs.getObject( 1 );
while( rs.next() ) {
  cs2 = ... selectType ( ?... );
  cs2.registerOutParameter...;
  cs2.execute();
  rs2 = ( ResultSet...;
  while( rs2.next() ) {
    cs3 = ...;
    ...;
    rs3 = ...;
    while( rs3.next() ) {
      cs4 = ...;
      ...;
      rs4 = ...;
      while( rs4.next() ) {
        ...;
      }
      rs4.close();
      cs4.close();
    }
    rs3.close();
    cs3.close();
  }
  rs2.close();
  cs2.close();
}
rs.close();
cs.close();
con.close();

So... I've been able to get this to work (though it's very slow) when I only run it for 1 dept (the first cs), but if I try to run it for everything... it takes 7 forevers, returns some data then dies giving me the following error:
java.sql.SQLException: No more data to read from socket
What does that mean... and/or how can I fix it? Is my code bad (is this bad practice?- I tried combining all the statements, but that required 5 joins- which took even longer)?
I'd appreciate any help.
Thanks,
-GL

[David O'Meara]

I'll probably get someone to move this to JDBC, it isn't a JSP question.
Dies on what line?
My guess is that it is a problem related to opening multiple ResultSets on the same Connection, but we can't be sure unless you're prepared to try it out.
If you have it working on an ugly join, can you optimise the SQL to speed that up? Not my forte, but a DBA should be able to cut the query right back.
Dave

[Mapraputa Is]

Moving to JDBC, as requested

[Jamie Robertson]

which line of code is throwing the exception?
Jamie