Last updated on NOVEMBER 04, 2016
Applies to:Oracle Tuxedo / Tuxedo /
Information in this document applies to any platform
PRODUCT: TUXEDO VERSION: 6.4 COMPONENT: WS PLATFORM: ALL PLATFORMS PATCHLEV64: 59 DESCRIPTION: DESCRIPTION: There are two different queues for each WSH, one is the communication events list and the other is the blocked event list. When WSH handler works under heavy load it starts to block, but WSH should never block since all the WSC will also block with it, thus it starts to queue some of the requests (it puts an entry into the blocked event list each time it discovers that it may block) and switch context to do other clients. Problem occurs later when WSH searches the blocked event list to start re sending the requests.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms