PH51980: ECLIPSELINK THROWS EXCEPTION ON DB2ZOS WHEN OBTAINING CURRENT TIMESTAMP

APAR status

• Closed as program error.

Error description

• EclipseLink executes the query "SELECT CURRENT TIMESTAMP FROM
  SYSIBM.SYSDUMMY1" when obtaining the current time from the
  database. This is usually done for version locking with
  java.sql.Timestamp types.
  
  For non-IBM JDKs and MIXED data types, this query throws an
  exception as an unexpected UNICODE type is returned
  
  Exception caught from before_completion synchronization
  operation: java.nio.charset.UnsupportedCharsetException: Cp1027
  	at java.base/java.nio.charset.Charset.forName(Charset.java:529)
  	at com.ibm.db2.jcc.am.r.<init>(Unknown Source)
  	at com.ibm.db2.jcc.am.q.a(Unknown Source)
  	at com.ibm.db2.jcc.am.Agent.getByteToCharConverter(Unknown
  Source)
  	at com.ibm.db2.jcc.t4.gc.a(Unknown Source)
  	at com.ibm.db2.jcc.t4.bb.a(Unknown Source)
  	at com.ibm.db2.jcc.t4.bb.a(Unknown Source)
  	at com.ibm.db2.jcc.t4.bb.a(Unknown Source)
  	at com.ibm.db2.jcc.t4.bb.n(Unknown Source)
  	at com.ibm.db2.jcc.t4.bb.j(Unknown Source)
  	at com.ibm.db2.jcc.t4.bb.d(Unknown Source)
  	at com.ibm.db2.jcc.t4.p.c(Unknown Source)
  	at com.ibm.db2.jcc.t4.vb.j(Unknown Source)
  	at com.ibm.db2.jcc.am.ip.mb(Unknown Source)
  	at com.ibm.db2.jcc.am.jp.b(Unknown Source)
  	at com.ibm.db2.jcc.am.jp.kc(Unknown Source)
  	at com.ibm.db2.jcc.am.jp.executeQuery(Unknown Source)
  	at
  com.ibm.ws.rsadapter.jdbc.WSJdbcPreparedStatement.executeQuery(W
  SJdbcPreparedStatement.java:475)
  	at
  org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor
  .executeSelect(DatabaseAccessor.java:1018)
  	at
  org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor
  .basicExecuteCall(DatabaseAccessor.java:653)
  	at
  org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor
  .executeCall(DatabaseAccessor.java:560)
  	at
  org.eclipse.persistence.internal.sessions.AbstractSession.basicE
  xecuteCall(AbstractSession.java:2070)
  	at
  org.eclipse.persistence.sessions.server.ClientSession.executeCal
  l(ClientSession.java:310)
  	at
  org.eclipse.persistence.internal.queries.DatasourceCallQueryMech
  anism.executeCall(DatasourceCallQueryMechanism.java:262)
  	at
  org.eclipse.persistence.internal.queries.DatasourceCallQueryMech
  anism.executeCall(DatasourceCallQueryMechanism.java:248)
  	at
  org.eclipse.persistence.internal.queries.DatasourceCallQueryMech
  anism.executeSelectCall(DatasourceCallQueryMechanism.java:332)
  	at
  org.eclipse.persistence.internal.queries.DatasourceCallQueryMech
  anism.executeSelect(DatasourceCallQueryMechanism.java:314)
  	at
  org.eclipse.persistence.queries.DataReadQuery.executeNonCursor(D
  ataReadQuery.java:197)
  	at
  org.eclipse.persistence.queries.DataReadQuery.executeDatabaseQue
  ry(DataReadQuery.java:152)
  	at
  org.eclipse.persistence.queries.DatabaseQuery.execute(DatabaseQu
  ery.java:910)
  	at
  org.eclipse.persistence.queries.DataReadQuery.execute(DataReadQu
  ery.java:137)
  	at
  org.eclipse.persistence.queries.DatabaseQuery.executeInUnitOfWor
  k(DatabaseQuery.java:809)
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server - Java Persistence API - JPA 2.1 &   *
  *                  EclipseLink                                 *
  ****************************************************************
  * PROBLEM DESCRIPTION: ECLIPSELINK THROWS EXCEPTION ON         *
  *                      DB2ZOS WHEN OBTAINING CURRENT           *
  *                      TIMESTAMP                               *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  EclipseLink uses this query for DB2 z/OS, to obtain Timestamps:
  ```
  SELECT CURRENT TIMESTAMP FROM SYSIBM.SYSDUMMY1
  ```
  Exception:
  ```
  Exception caught from before_completion synchronization
  operation: java.nio.charset.UnsupportedCharsetException: Cp1027
  at java.base/java.nio.charset.Charset.forName(Charset.java:529)
  at com.ibm.db2.jcc.am.r.<init>(Unknown Source)
  at com.ibm.db2.jcc.am.q.a(Unknown Source)
  ```
  

Problem conclusion

• The fix for this APAR changes the EclipseLink implementation
  and involves an update to the third-party source. See
  https://github.com/eclipse-ee4j/eclipselink/issues/1779
  
  This fix is currently targeted for WebSphere Application
  Server 9.0.5.16 and WebSphere Liberty 23.0.0.4. For more
  information, see 'Recommended Updates for
  WebSphere Application Server':
  https://www.ibm.com/support/pages/node/715553
  

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

  WEBSPHERE APP S

• Fixed component ID

  5724J0800

Applicable component levels