IBM Support

PI74104: EclipseLink might add unused table in generated query

Fixes are available

9.0.0.4: WebSphere Application Server traditional V9.0 Fix Pack 4
9.0.0.5: WebSphere Application Server traditional V9.0 Fix Pack 5
9.0.0.6: WebSphere Application Server traditional V9.0 Fix Pack 6
9.0.0.7: WebSphere Application Server traditional V9.0 Fix Pack 7
17.0.0.1: WebSphere Application Server Liberty 17.0.0.1
17.0.0.2: WebSphere Application Server Liberty 17.0.0.2
17.0.0.3: WebSphere Application Server Liberty 17.0.0.3
17.0.0.4: WebSphere Application Server Liberty 17.0.0.4
18.0.0.1: WebSphere Application Server Liberty 18.0.0.1
18.0.0.2: WebSphere Application Server Liberty 18.0.0.2
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
18.0.0.3: WebSphere Application Server Liberty 18.0.0.3
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
18.0.0.4: WebSphere Application Server Liberty 18.0.0.4
19.0.0.1: WebSphere Application Server Liberty 19.0.0.1
19.0.0.2: WebSphere Application Server Liberty 19.0.0.2
19.0.0.3: WebSphere Application Server Liberty 19.0.0.3
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
19.0.0.4: WebSphere Application Server Liberty 19.0.0.4
19.0.0.5: WebSphere Application Server Liberty 19.0.0.5
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
19.0.0.6: WebSphere Application Server Liberty 19.0.0.6
19.0.0.7: WebSphere Application Server Liberty 19.0.0.7
19.0.0.8: WebSphere Application Server Liberty 19.0.0.8
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
19.0.0.9: WebSphere Application Server Liberty 19.0.0.9
19.0.0.10: WebSphere Application Server Liberty 19.0.0.10
19.0.0.11: WebSphere Application Server Liberty 19.0.0.11
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
19.0.0.12: WebSphere Application Server Liberty 19.0.0.12
20.0.0.1: WebSphere Application Server Liberty 20.0.0.1
20.0.0.2: WebSphere Application Server Liberty 20.0.0.2
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
20.0.0.3: WebSphere Application Server Liberty 20.0.0.3
20.0.0.4: WebSphere Application Server Liberty 20.0.0.4
20.0.0.5: WebSphere Application Server Liberty 20.0.0.5

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When migrated  application from Liberty Profile 8.5.5.6
    OpenJPA to Liberty Profile 16.0.0.3 with JPA 2.1 and
    EclipseLink.
    After run class SubQueryIssue, the generated query:
    SELECT COUNT(DISTINCT(t0.PERS_OBJ_ID)) FROM
    T_FACT_WORK_ASGNMT
    t0, T_DIM_PAY_GRP t2, T_RPT_TO_HRCHY t1 WHERE
    ((((t1.CLNT_OBJ_ID = t0.
    CLNT_OBJ_ID) AND (t0.MNGR_PERS_OBJ_ID =
    t1.MNGR_PERS_OBJ_ID))
    AND (t1.
    LOGIN_MNGR_PERS_OBJ_ID = ?)) OR EXISTS (SELECT
    t3.PERS_OBJ_ID
    FROM
    T_USR_ADDL_ACCS t3 WHERE ((((t3.CLNT_OBJ_ID =
    t0.CLNT_OBJ_ID)
    AND (t3.
    MNGR_PERS_OBJ_ID = ?)) AND (t3.WORK_ASGNMT_NBR =
    t0.WORK_ASGNMT_NBR))
    AND (t3.PERS_OBJ_ID = t0.PERS_OBJ_ID))) )
    bind => [MyOrgOID, MyUserOID]
    
    The table T_DIM_PAY_GRP is part of the query but it's not
    used at all.
    
    
     
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server Liberty - Java Persistence API       *
    *                  (JPA)                                       *
    ****************************************************************
    * PROBLEM DESCRIPTION: When using a SubQuery within a          *
    *                      CriteriaQuery, EclipseLink might add    *
    *                      an                                      *
    *                      unused table in the generated query's   *
    *                      FROM clause                             *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When using the jpa-2.1 feature with the default provider,
    EclipseLink, and using a SubQuery within a CriteriaQuery with
    multiple roots, the generated query might include one of the
    CriteriaQuery's roots in the FROM clause that is not used in
    the
    SQL statement.
    

Problem conclusion

  • When a CriteriaQuery with multiple roots has a SubQuery, the
    generated query will only include tables that are in use within
    the query's FROM clause.
    
    The fix for this APAR is currently targeted for inclusion in
    Service Level (Fix Pack) 9.0.0.4 of WebSphere
    Application Server version 9.0.0 and in fix
    pack 17.0.0.1 for WebSphere Application Server Liberty.
    Please refer to the Recommended Updates page for
    delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

  • Only add CriteriaQuery roots that will be used in the query.
    More specifically, do not call CriteriaQuery.from() method on a
    table that will not be used in the query.
    

Comments

APAR Information

  • APAR number

    PI74104

  • Reported component name

    LIBERTY PROFILE

  • Reported component ID

    5724J0814

  • Reported release

    855

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-12-21

  • Closed date

    2017-02-14

  • Last modified date

    2017-03-23

  • 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

  • R855 PSY

       UP

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

Document Information

Modified date:
17 June 2020