Hi everybody,
I've servlets accessing different data sources.  One of the data source is
not very reliable and drops from the network from time to time.  When this
data-source is not reachable, it takes about 30 seconds for each call to
DriverManager.getConnection() to throw an exception.  And impatient retries
from users make matters worse.
All subsequent DriverManger.getConnection() calls get queued up (since the
method is synchronised), even for those accessing other data-sources.

Is there any way I can reduce the time-out for the getConnection() call in
such a case of communications failure? DriverManager.setLoginTimeout()
doesn't help.  Or any suggestions on how I can handle this 'unreliable'
source without seriously affecting the getConnection()'s to the other
data-sources?

Thanks.

___________________________________________________________________________
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

Reply via email to