Duplicate Transmissions Sent To OTM Due To Closed TCP/IP Connection: TCP/IP FIN Being Sent
(Doc ID 1492463.1)
Last updated on SEPTEMBER 08, 2016
Applies to:Oracle Transportation Management - Version 5.5 and later
Information in this document applies to any platform.
OTM received inbound integrations via HTTP POST on a dedicated Apache / Tomcat server. Observed that frequently the Apache / Tomcat server closes the TCP/IP connection before replying to the sender and after receiving and persisting the transmission to the database. Apache logs indicate that it is replying to the sender with an HTTP 200 however, a network trace observed the Apache server tearing down the connection by sending a TCP/IP FIN. This typically happens when OTM takes more than 30 seconds to persist the transmission and related transactions to the database and so it affects typically transmissions with high transaction counts.
The resulting effect is that the sending side retransmits the same integration over and over. This causes huge backlogs in the publishWait and agentUtility queues and further slows OTM's ability to respond causing more resends and larger backlogs eventually resulting in having to restart the application.
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