Home/ Questions/Q 448213
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-12T21:38:50+00:00

Sometimes when I call connect() on a third-party proprietary JDBC driver, it never returns

  • 0

Sometimes when I call connect() on a third-party proprietary JDBC driver, it never returns and a stack trace shows that it is stuck waiting for a socket read (usually). Is there a generic way to forcibly cancel this operation from another thread? It’s a blocking I/O call so Thread.interrupt() won’t work, and I can’t directly close the socket because I don’t have access to it since it’s created inside the proprietary code.

I’m looking for generic solutions because I have a heterogeneous DB environment (Oracle, MySQL, Sybase etc). But driver-specific suggestions are also welcome. Thanks,

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    There is no standard JDBC interface to set connection or read timeouts, so you are bound to use proprietary extensions, if the JDBC driver supports timeouts at all. For the Oracle JDBC thin driver, you can e.g. set the system properties “oracle.net.CONNECT_TIMEOUT” and or “oracle.jdbc.ReadTimeout” or pass a Properties instance to DriverManager.getConnection with these properties set. Although not particulary well documented, the Oracle specific properties are listed in the API documentation.

    For other JDBC drivers, the documentation should contain the relevant references.

    • 0