Fixes are available
8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
APAR status
Closed as program error.
Error description
Description: If an EJBQL query contains a join in the FROM clause (for example, "IN a.b.c.d dGroup") where a middle element (b in this case) utilizes inheritance (for example, "b extends b_super") and there exists a predicate in the WHERE clause that navigates a common path (that includes the inheritance-utilizing entity type) as the join defined in the FROM clause (for example, "WHERE a.b.x.id = ?") and the terminal entity in that predicate also utilizes inheritance (for example, x extends x_super), then the query processing engine can fail and silently produce invalid SQL for the query. The problem does not show up if no entities in the FROM clause join statement or the WHERE clause predicate use inheritance.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server * **************************************************************** * PROBLEM DESCRIPTION: A complex EJB-QL query involving FROM- * * clause joins and entity bean class * * inheritance yields invalid generated * * SQL. * **************************************************************** * RECOMMENDATION: * **************************************************************** The EJB-QL parser has been found to improperly generate SQL with queries that match the following cumulative criteria: The EJB-QL query contains a join in the FROM clause (i.e., ¢â‚¬ “FROM Entity a, IN (a.b.c.d) dGroup ¢â‚¬ ½) The EJB-QL query contains a predicate that navigates across an inner path element also associated with the FROM clause join (i.e., ¢â‚¬ “WHERE a.b.g.id = :?1 ¢â‚¬ ½) One or more of the non-leaf path entities in the FROM join utilize entity type inheritance (i.e., b extends b_super) The entity addressed by the common path element in the predicate also utilizes entity type inheritance (i.e., g extends g_super)
Problem conclusion
The EJB Query processor will emit a ¢â‚¬ “WQRY1113E ¢â‚¬ ½ war may indicate that this scenario has been encountered. The problem has been determined to be a Permanent Restriction and will not be fixed in the service stream. The code change to emit the warning message is currently targeted for inclusion in fix pack 8.5.5.4. 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 number
PI20701
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2014-06-25
Closed date
2014-09-30
Last modified date
2014-09-30
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
WEBS APP SERV N
Fixed component ID
5724H8800
Applicable component levels
R60A PSY
UP
R60H PSY
UP
R60I PSY
UP
R60P PSY
UP
R60W PSY
UP
R60Z PSY
UP
R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61W PSY
UP
R61Z PSY
UP
R700 PSY
UP
R800 PSY
UP
R850 PSY
UP
Document Information
Modified date:
27 April 2022