PH42468: WEBCONTAINER THREADS HUNG WHILE CLOSING WEBSOCKETS

APAR status

• Closed as program error.

Error description

• WebContainer threads hung while closing WebSockets
  
  com/ibm/ws/wsoc/WsocConnLink.finishReadBeforeClose
  
  hang seen when using WAS v9.0.5.7 , PH18898 & PH30163 applied.
  
  [11/11/21 13:54:49:476 CET] 000000c6 ThreadMonitor W WSVR0605W:
  Thread "WebContainer : 1" (0000020d) has been active for 17823
  milliseconds and may be hung. There is/are 1 thread(s) in total
  in the server that may be hung.
  at java.lang.Object.wait(Native Method)
  at java.lang.Object.wait(Object.java:189)
  at com.ibm.ws.wsoc.WsocConnLink.finishReadBeforeClose(WsocConnL
  ink.java:812)
  at com.ibm.ws.wsoc.SessionImpl.close(SessionImpl.java:394)
  at com.ibm.ws.wsoc.EndpointManager.httpSessionExpired(EndpointM
  anager.java:166)
  at com.ibm.ws.wsoc.WsocHttpSessionListener.sessionDestroyed(Wso
  cHttpSessionListener.java:63)
  at com.ibm.ws.webcontainer.managedobject.ManagedObjectListenerW
  rapper.sessionDestroyed(ManagedObjectListenerWrapper.java:90)
  at com.ibm.ws.session.http.HttpSessionObserver.sessionDestroyed
  (HttpSessionObserver.java:202)
  at com.ibm.ws.session.SessionEventDispatcher.sessionDestroyed(S
  essionEventDispatcher.java:160)
  at com.ibm.ws.session.StoreCallback.sessionInvalidated(StoreCal
  lback.java:126)
  at com.ibm.ws.session.store.memory.MemorySession.invalidate(Mem
  orySession.java:226)
  at com.ibm.ws.session.http.HttpSessionImpl.invalidate(HttpSessi
  onImpl.java:303)
  at
  com.ibm.ws.session.SessionData.invalidate(SessionData.java:247)
  at com.ibm.ws.session.HttpSessionFacade.invalidate(HttpSessionF
  acade.java:200)
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server                                      *
  *                  WebSocket using secure sessions.            *
  ****************************************************************
  * PROBLEM DESCRIPTION: A thread hangs when a secure WebSocket  *
  *                      session has timed out and               *
  *                      WebSocket é ástarts closing the
  *                      connection.                             *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When WebSocket determines that a session on a secure connection
  has timed out, it initiates closing of the connection. é á Durin
  this process, a WebContainer thread may é áhang indefinitely.
  

Problem conclusion

• After a secure WebSocket times out, the connection is closed
  properly.
  
  The fix for this APAR is targeted for inclusion in fix pack
  9.0.5.12 and Liberty 22.0.0.5 via OLGH20676.
  
  For more information, see 'Recommended Updates for
  WebSphere Application Server':
  https://www.ibm.com/support/pages/node/715553
  

Temporary fix

Comments

APAR Information

• 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