Fixes are available
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
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
Situation: Customer has nested Asynchronous method calls where asynchronous method A calls B which calls C. A -> B -> C. A and B then call Future.get(timeout,unit). If C hangs, B's Future.get(timeout,unit) will not honor the timeout and will be stuck. The timeout is only honored in A, which will eventually throw a TimeoutException. Method B never completes. After this fix, the timeout in B is honored and will throw the TimeoutException, and then continue as long as the timeout in A is greater than the timeout in B.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server using nested EJB Asynchronous * * method calls * **************************************************************** * PROBLEM DESCRIPTION: Nested EJB Asynchronous method calls * * not honoring nested * * Future.get(timeout, * * unit) timeouts. * **************************************************************** * RECOMMENDATION: * **************************************************************** Situation: Customer has nested Asynchronous method calls where asynchronous method A calls B which calls C. A -> B -> C. A and B then call Future.get(timeout,unit). If C hangs, B's Future.get(timeout,unit) will not honor the timeout and will be stuck. The timeout is only honored in A, which will eventually throw a TimeoutException. Method B never completes. After this fix, the timeout in B is honored and will throw the TimeoutException, and then continue as long as the timeout in A is greater than the timeout in B.
Problem conclusion
The fix for this APAR is currently targeted for inclusion in fix pack 9.0.0.9 and 8.5.5.15 for WebSphere Application Server traditional and 18.0.0.3 for WebSphere Liberty. 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
PI96086
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2018-04-02
Closed date
2018-08-06
Last modified date
2018-08-06
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
R850 PSY
UP
R900 PSY
UP
Document Information
Modified date:
27 April 2022