My Oracle Support Banner

RP/TUX 10.0 - WSH did not check if the TMALARM message is stale (Doc ID 778100.1)

Last updated on JANUARY 19, 2018

Applies to:

Oracle Tuxedo / Tuxedo / 10.0
Information in this document applies to any platform

Goal

DESCRIPTION:
WSH did not check if the TMALARM message is stale.
 
In the client machine, start up 100 WSC clients. The result is some clients can return normally, but some clients hang
at tpcall(). Using the dbx to attach the client's process, the client's information is as following:
=>[1] _so_recv(0x172, 0x16b95d0, 0xfa0, 0x0, 0xd4, 0x1e920), at 0xfee1c768 
  [2] _e_net_rcvraw(0x16d, 0x28c8, 0x168, 0x, 0xff2ccdbc, 0x14), at 0xff2ae524 
  [3] _e_net_recv(0x43518, 0x200016d, 0x0, 0x14, 0x28c8, 0x1b0b928), at 0xff2b8e54 
  [4] tl_ssl_read_callback(0xfe27ba58, 0xfe27ba6c, 0x183d9d0, 0xeec380, 0xff386f9c, 0x43518), at 0xff 
  [5] _tmf90086(0xfe27bae8, 0x1888d90, 0x5, 0xfffffff8, 0xeec380, 0x0), at 0xe59ff9a0 
  [6] _tmf90173(0x288ee68, 0x3e28, 0x0, 0xfe27bc2c, 0x1888d90, 0xfe27baf0), at 0xe5a0122c 
  [7] Mutex_tmf90173(0x288ec90, 0xfe27bc2c, 0x1888d90, 0xffffe400, 0x183da30, 0x183d9d0), at 0xe5a38f3c 
  [8] br_e_net_recv(0x43518, 0x200016d, 0xfe27bc24, 0xfe27bc2c, 0xfe27bc28, 0x288ec90), at 0xff363a08 
  [9] _wsc_nw_msgrcv(0x43518, 0xfe27bcc0, 0xfe27bcbc, 0x5, 0x0, 0x6426c), at 0xff31fad4 
  [10] _wsc_msgrcv(0x43518, 0x53115c, 0xfe27be38, 0x5, 0x0, 0x), at 0xff322e10 
  [11] _wsc_getrply(0x43518, 0x53115c, 0x80000, 0x1, 0x5, 0x0), at 0xff 
  [12] _tpcall_internal(0x43518, 0x0, 0xab5778, 0xfe27bf1c, 0x53115c, 0x), at 0xff3190ac 
  [13] tpcall(0x225c8, 0x5523e0, 0x0, 0xfe27bf84, 0xfe27bf8c, 0x0), at 0xff318a08 

CONFIGURATION:
Tuxedo 10.0

Solution

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
  Goal
  Solution
  References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.