Tuxedo 8.1 and 9.1 - Multithreaded Client Dumps a Core When -N is Set for WSL
Last updated on JANUARY 12, 2016
Applies to:Oracle Tuxedo - Version 8.1 to 9.1
Information in this document applies to any platform.
Information in this document applies to any platform
Tux 8.1 64bit RP 159
Solaris 5.8 64bit
When WSL is set with "-N 5", the multithreaded client dumps a core.
The same test works without "-N".
This CR is related to the CR209886 that solved WSL -N performance issue.
The same test has been run with DIPIN, SIGNAL, THREAD and IGNORE mode. They all have problems with "WSL -N 5"
Stack trace is as follows:
 _e_net_opencursor(0x100144450, 0xffffffff7b407420, 0x1388, 0xffffffff7b40742c, 0xffffffff7ef1fec0,
0xffffffff7ef21460), at 0xffffffff7ee0bd5c
 _wsc_nw_msgrcv(0x100144450, 0xffffffff7b407530, 0xffffffff7b40752c, 0x5, 0x5, 0x1001aefe0), at
 _wsc_msgrcv(0x100144450, 0x1001472f8, 0xffffffff7b407824, 0x5, 0x0, 0x0), at 0xffffffff7f3242a0
 _wsc_getrply(0x100144450, 0x1001472f8, 0x1001af360, 0x1, 0x0, 0x5), at 0xffffffff7f32238c
 _tpcall_internal(0x100144450, 0x0, 0x80000, 0xffffffff7b4079c8, 0x1001472f8, 0xffffffffffffffff), at
 tpcall(0x100101e30, 0x1001e3ff8, 0x0, 0xffffffff7b407a98, 0xffffffff7b407a88, 0x0), at 0xffffffff7f31a0f0
 tuxCall(0x4a, 0x14, 0xffffffff7dcc4c90, 0x0, 0x0, 0x1001e3ff8), at 0x100001198
 thread_function(0xa, 0xffffffff7be053a1, 0xffffffff7dcc31b8, 0x0, 0x4a, 0xa), at 0x1000012b4
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