PH13031: ORACLE.JDBC.READTIMEOUT SETTING NOT WORKING USING EITHER JDBC-4.1 OR JDBC-4.2 FEATURES

9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3

APAR status

• Closed as program error.

Error description

• Running WebSphere Liberty Profile 19.0.0.1,
  
  oracle.jdbc.ReadTimeout=21000 setting not working, using
  either
  
  jdbc-4.1 or jdbc-4.2 features (jdbc-4.0 feature works -
  same
  
  code, application server, driver/database). Also, this works
  in
  
  WAS ND 8.5.5.11
  
  
  
  ReadTimeout parameter is working for getConnection, but not
  for
  
  executeQuery.
  

Local fix

• Using jdbc-4.0 feature.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server v9.0 using a JDBC driver that        *
  *                  manually sets the network timeout.          *
  ****************************************************************
  * PROBLEM DESCRIPTION: java.sql.Connection's network timeout   *
  *                      not getting set to the correct value.   *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Starting with JDBC 4.1, java.sql.Connection can have a network
  timeout configured on it. This timeout value can incorrectly get
  reset to 0 (no timeout) if a JDBC driver provides its own
  property/mechanism for setting the network timeout outside of
  the Connection.setNetworkTimeout() method.
  
  Specifically this has been observed with Oracle's JDBC 4.1+
  drivers when the oracle.jdbc.ReadTimeout is specified via
  connectionProperties on a datasource.
  

Problem conclusion

• The JDBC code has been updated to differentiate between an
  uninitialized network timeout (use WebSphere's default) and a
  JDBC driver provided default.
  
  The fix for this APAR is currently targeted for inclusion in fix
  pack 9.0.5.2.  Please refer to the Recommended Updates page for
  delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  LIBERTY PROFILE

• Fixed component ID

  5724J0814

Applicable component levels

• R855 PSY

     UP