WS Context Seems To Get Corrupted After Exiting A Fork() on Oracle Tuxedo
(Doc ID 2891547.1)
Last updated on AUGUST 24, 2022
Applies to:Oracle Tuxedo - Version 12.2.2 and later
Information in this document applies to any platform.
On: 12.2.2 version, Tuxedo Kernel
Calling Tuxedo service from Batch using WS Client Server
All works well until we issue a fork() and exit() then get the error "LIBWSC_CAT:1037"
Seems that the call to exit() from the fork process corrupted the WS context.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document