IBM Support

PH10785: JAVAX.PERSISTENCE.LOCK.TIMEOUT WORKS INCORRECTLY

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

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

Temporary fix

Comments

APAR Information

  • APAR number

    PH10785

  • Reported component name

    LIBERTY PROFILE

  • Reported component ID

    5724J0814

  • Reported release

    CD0

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-04-10

  • Closed date

    2019-08-07

  • Last modified date

    2019-11-21

  • 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

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"CD0","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
21 November 2019