PH10785: JAVAX.PERSISTENCE.LOCK.TIMEOUT WORKS INCORRECTLY

APAR status

• Closed as program error.

Error description

• The customer thought that the value of
  ´javax.persistence.lock.timeout´ would be changed to
  MILLISECONDS if the following content was set in
  persistence.xml.
  
  <property name = "eclipselink.query.timeout.unit" value =
  "MILLISECONDS" />
  
  However, the EclipseLink persistence property ´eclipselink.query
  to configure the value of the JPA persistence property
  ´javax.persistence.query.timeout´. There currently does not
  exist an EclipseLink persistence property that will allow
  ´javax.persistence.lock.timeout´ to be configured.
  

Local fix

• No
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server - Java Persistence API - JPA 2.1 &   *
  *                  EclipseLink                                 *
  ****************************************************************
  * PROBLEM DESCRIPTION: EclipseLink applies the                 *
  *                      "javax.persistence.lock.timeout" &      *
  *                      "javax.persistence.query.timeout"       *
  *                      propertys value as seconds rather than  *
  *                      milliseconds                            *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The EclipseLink persistence provider applies the value for the
  "javax.persistence.lock.timeout" &
  ""javax.persistence.query.timeout" persistence property in
  seconds. According to section 3.4.4.3 of the JPA specification,
  the value provided is in milliseconds. However, EclipseLink
  directly passes this value to the preparedstatement, which
  expects a value in seconds. Since there is no conversion, the
  value passed in the property is treated as seconds instead of
  milliseconds.
  

Problem conclusion

• The fix for this APAR changes the EclipseLink implementation and
  involves an update to the thirdparty source. See
  https://bugs.eclipse.org/bugs/show_bug.cgi?id=533724
  
  This fix is currently targeted for WebSphere Application Server
  9.0.5.1, 8.5.5.16, and WebSphere Liberty 19.0.0.6.  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