Yes, but it can��t be avoided as when the servlet found that db operation
throw exception (most likely that the exception is caused by connection
problem), it will try to re-connect to the database. It is this
re-connection takes very long time and browser can��t wait. My only
intention is try to inform the user there is db problem instead of browser
timeout.
Kenneth
-----Original Message-----
From: Andy Bailey [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, November 09, 1999 9:09 PM
To: [EMAIL PROTECTED]
Subject: Re: getConnection takes very long time to
timeout
Dear ALL
I encountered one serious problem with JDBC getConnection
that it waits very
very long time (> 4 mins) when there is network problem
between web server
and database server. Browsers can��t wait that long time and
timeout. But we
want to print a message to user that database connection
error occurred
I��m using classes12.zip thin client from Oracle.
Does anyone know how to shorten the getConnection timeout ?
This depends on your server really.
Also, I would avoid trying to make and destroy db
connections on the fly
as you seem to be doing, it causes the very problems you are
experiencing.
Andy Bailey
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and
include in the body
of the message "signoff SERVLET-INTEREST".
Archives:
http://archives.java.sun.com/archives/servlet-interest.html
Resources:
http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
