RP/TUX Tuxedo /WS Context Leaks When tpcall() Fails With LIBWSC_CAT:1011
Last updated on MAY 01, 2017
Applies to:Oracle Tuxedo - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
If a Tuxedo worstation handler (also known as WSH) process is shutdown before the workstation client (also known as /WS client) is calling tpcall(), it fails with TPESYSTEM and LIBWSC_CAT:1011 outputs in ULOG.
It is expected behavior. However if the /WS client is using multicontext mode the context will not cleanup even if tpterm() is called.
After tpinit() with TPMULTICONTEXTS flag called, the context number will be increased and never cleanup old contexts.
If it happen 1023 times, tpinit() fails with " LIBWSC_CAT:1901:ERROR: Failed to create a new context in multi-context mode " due to reach max number of context.
This problem happen if server side is Windows.
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