PI75512: Cleanup up websocket connection when outbound connection attempt fails at the app server

Fixes are available

APAR status

Closed as program error.

Error description

Clean up wsoc and channel objects when the outbound
connection makes the TCP/IP connection ok, but then the
websocket connection to the ap server is rejected by the app
server (for example, with a 500 error).

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server who have websocket programs doing    *
*                  outbound connections                        *
****************************************************************
* PROBLEM DESCRIPTION: If a websocket outbound connection      *
*                      attempt fails an object may be leaked,  *
*                      which can accumulate over time to       *
*                      resource depletion                      *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
If the user application at the WebSphere Application Server does
an outbound websocket connection request, and that request fails
to connect, then the connection objects may not be released for
garbage collection.  Over time this can cause resource depletion
(OutOfMemory, slow running server, etc....)

Problem conclusion

All the connection objects are now released if the outbound
websocket connection attempt fails.

The fix for this APAR is currently targeted for inclusion in fix
pack 17.0.0.2  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
PI75512
Reported component name
WAS LIBERTY COR
Reported component ID
5725L2900
Reported release
CD0
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-01-26
Closed date
2017-03-07
Last modified date
2017-03-07

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
WAS LIBERTY COR
Fixed component ID
5725L2900

Applicable component levels

RCD0 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSD28V","label":"WebSphere Application Server Liberty Core"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"CD0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
04 May 2022

Tips

PI75512: Cleanup up websocket connection when outbound connection attempt fails at the app server

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

RCD0 PSY

Document Information

Share your feedback

Need support?