Tuxedo WSH Process Sending Some Data After /WS Client Closed The Connection
(Doc ID 1634734.1)
Last updated on MAY 19, 2021
Applies to:
Oracle Tuxedo - Version 10.3.0 and laterInformation in this document applies to any platform.
Symptoms
A Tuxedo WSH process sends some data after the corresponding /WS client closed the connection. This causes the OS to send a RST message back to the WSH side(instead of a FIN message).
From network package capture we find:
37 2014-02-10 13:44:43.175879 X.X.X.X X.X.X.X TCP 68 59529 >15939 [FIN, ACK] Seq=2021 Ack=1353 Win=39296 Len=0 TSval=2847734348 TSecr=2847734348
38 2014-02-10 13:44:43.175884 X.X.X.X X.X.X.X TCP 372 15939 >59529 [PSH, ACK] Seq=1353 Ack=2022 Win=42624 Len=304 TSval=2847734348 TSecr=2847734348
39 2014-02-10 13:44:43.175892 X.X.X.X X.X.X.X TCP 56 59529 >15939 [RST] Seq=2022 Win=0 Len=0
38 2014-02-10 13:44:43.175884 X.X.X.X X.X.X.X TCP 372 15939 >59529 [PSH, ACK] Seq=1353 Ack=2022 Win=42624 Len=304 TSval=2847734348 TSecr=2847734348
39 2014-02-10 13:44:43.175892 X.X.X.X X.X.X.X TCP 56 59529 >15939 [RST] Seq=2022 Win=0 Len=0
The client side connection disconnects but the Tuxedo WSH side connection remains(a noticeable problem with a firewall).
Cause
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
| Symptoms |
| Cause |
| Solution |
| References |