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 xample, "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 element (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 * * Versions 8.5.X * **************************************************************** * PROBLEM DESCRIPTION: Invalid SQL code may be produced in * * join clauses by EJBDeploy * **************************************************************** * RECOMMENDATION: * **************************************************************** 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 element (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
Problem conclusion
A warning message was added to indicate that invalid SQL code may be produced under certain circumstances. The fix for this APAR 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
PI21937
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-07-15
Closed date
2014-10-29
Last modified date
2014-10-29
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
R700 PSY
UP
R800 PSY
UP
R850 PSY
UP
Document Information
Modified date:
27 April 2022