PM89267: INCORRECT DATASOURCE CLASS INFERRED BY LIBERTY PROFILE WHEN LIBR ARY CONTAINS BOTH DERBY NETWORK CLIENT AND DERBY EMBEDDED JARS

8.5.5.1: WebSphere Application Server V8.5.5 Fix Pack 1
8.5.5.2: WebSphere Application Server V8.5.5 Fix Pack 2
8.5.5.3: WebSphere Application Server V8.5.5 Fix Pack 3
8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14

APAR status

• Closed as program error.

Error description

• When a data source is configured with
  properties.derby.embedded and the library contains both Derby
  Network Client and Derby Embedded jars and data source
  implementation class is not explicity specified on the
  jdbcDriver, then the configured dataSource is unusable and
  fails with an error like:
  java.sql.SQLNonTransientException: java.net.ConnectException :
  Error connecting to server localhost on port 1527 with message
  Connection refused: connect. DSRA0010E: SQL State = 08001,
  Error Code = 40,000
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server Liberty Profile                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: Incorrect JDBC driver type is guessed   *
  *                      when the jdbcDriver element             *
  *                      specifies multiple JDBC drivers.        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The nested vendor properties element is ignored when
  identifying the JDBC driver.
  

Problem conclusion

• The type of the nested vendor properties element is now taken
  into account when identifying the JDBC driver. For example,
  properties.derby.embedded indicates the Derby Embedded JDBC
  driver and properties.derby.client indicates the Derby Network
  Client JDBC driver.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.5.5.1. 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

• R850 PSY

     UP