It's probaly not a timeout of the connection object, but one of the database server. If the database server has a timeout for open connections, the connection on the driver side is 'open' but not functional any more. What exactly happens depends on the driver. (I've seen posts where people reported that isClosed() still return false in such a case for a certain driver). My last contact with oracle is to long ago to be more specific. But I know that there is a default timeout for connections in oracle (No, I can't remember how to query or set it).
> -----Ursprüngliche Nachricht----- > Von: Christian J. Dechery [mailto:[EMAIL PROTECTED]] > Gesendet: Mittwoch, 12. Juni 2002 14:01 > An: [EMAIL PROTECTED] > Betreff: RE: getting exception when trying to close connection > > A timeout on the Connection obj is also hard to believe... > even because when I debugged it with a page opening 10 > connections (just for testing, I don't have such a page)... 3 > of them didn't close... and it was not the last three... just > some random conns... > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
