Fixes are available
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
The Liberty websocket client might miss incoming data if communicating with a server that sends websocket data immediately after sending the HTTP 101 upgrade headers. An example of this problematic sequence is Liberty's websocket client communicating with a server that sends a message in a websocket endpoint onOpen method.. This problem usually presents itself when the websocket client is slow to read data, such as the websocket client running Liberty profile server that is under load.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server Liberty Profile * **************************************************************** * PROBLEM DESCRIPTION: Websocket client code can miss * * processing incoming data that is * * received immediately after HTTP upgrade * * response headers. * **************************************************************** * RECOMMENDATION: * **************************************************************** The Liberty websocket client might miss incoming data if communicating with a server that sends websocket data immediately after sending the HTTP 101 upgrade headers. An example of this problematic sequence is Liberty's websocket client communicating with a server that sends a message in a websocket endpoint onOpen method.. This problem usually presents itself when the websocket client is slow to read data, such as the websocket client running Liberty server that is under load.
Problem conclusion
Liberty websocket client code was fixed to correctly account for the extra data sent after the HTTP 101 upgrade headers. The fix for this APAR is currently targeted for inclusion in fix pack 8.5.5.5. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
When using the Liberty websocket client in a situation where you control the websocket content sent by the server, avoid sending websocket data immediately after the HTTP 101 upgrade headers are sent. The typicaly place where this would occur would be sending websocket data in a server endpoints onOpen method.
Comments
APAR Information
APAR number
PI32942
Reported component name
LIBERTY PROFILE
Reported component ID
5724J0814
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2015-01-19
Closed date
2015-01-21
Last modified date
2015-01-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
R850 PSY
UP
Document Information
Modified date:
27 April 2022