Release Notes
Abstract
EclipseLink violates the JPA 2.1 specification by using the values from "javax.persistence.lock.timeout" and "javax.persistence.query.timeout" as SECONDS, rather than MILLISECONDS
Content
Starting with WebSphere Liberty 19.0.0.6, the persistence properties "javax.persistence.lock.timeout" and "javax.persistence.query.timeout" value will be read by EclipseLink in MILLISECONDS per the JPA specification.
This fix can be reverted to it's original behavior by specifying the following persistence property in the persistence.xml:
<!-- For property "javax.persistence.lock.timeout" configuration --><property name="eclipselink.pessimistic.lock.timeout.unit" value="SECONDS"/><!-- For property "javax.persistence.query.timeout" configuration --><property name="eclipselink.query.timeout.unit" value="SECONDS"/>
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSD28V","label":"WebSphere Application Server Liberty Core"},"Component":"JPA","Platform":[{"code":"PF016","label":"Linux"},{"code":"PF017","label":"Mac OS"},{"code":"PF033","label":"Windows"}],"Version":"19.0.0.6","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Was this topic helpful?
Document Information
Modified date:
26 August 2019
UID
ibm10967687