My Oracle Support Banner

Large Number of DAP (Data Access Pack) TCP Sockets have CLOSE_WAIT Status (Doc ID 1552849.1)

Last updated on FEBRUARY 21, 2019

Applies to:

Oracle Communications Network Charging and Control - Version 5.0.0 to 5.0.1 [Release 5.0]
Information in this document applies to any platform.

Symptoms

The Data Access Pack (DAP) application is not closing down its TCP port connections which are left in CLOSE_WAIT state.  These TCP ports remain in the CLOSE_WAIT state and are not cleared out and accumulate over time.

Example of problem scenario: 

Setup:


1. DAP establishes a connection

2. DAP message is sent out, the message is sent successfully
   TCP connection Status: 
 

  Fri Apr  5 12:43:28 GMT 2013
 

$ netstat -na |grep <IP>.8001
<IP>.48462   <IP>.8001    130880      0 139264      0 
ESTABLISHED 
<IP>.40669   <IP>.8001    130880      0 139264      0 CLOSE_WAIT 
<IP>.60438   <IP>.8001    130880      0 139264      0 CLOSE_WAIT 
<IP>.35789   <IP>.8001    130880      0 139264      0 CLOSE_WAIT 
<IP>.41044   <IP>.8001    130880      0 139264      0 CLOSE_WAIT 
<IP>.34035   <IP>.8001    130880      0 139264      0 CLOSE_WAIT 
<IP>.45899   <IP>.8001    130880      0 139264      0 CLOSE_WAIT  

3. After 30 seconds inactivity, the remote server decides to close the TCP connection and initiates the TCP disconnection procedure to DAP
4. DAP gets the fin and turns its TCP port into CLOSE-WAIT
   TCP connection status:

 
  Fri Apr  5 12:44:02 GMT 2013 

$ netstat -na |grep <IP>.8001
<IP>.48462   <IP>.8001    130880      0 139264      0 
CLOSE_WAIT 
<IP>.40669   <IP>.8001    130880      0 139264      0 CLOSE_WAIT 
<IP>.60438   <IP>.8001    130880      0 139264      0 CLOSE_WAIT 
<IP>.35789   <IP>.8001    130880      0 139264      0 CLOSE_WAIT 
<IP>.41044   <IP>.8001    130880      0 139264      0 CLOSE_WAIT 
<IP>.34035   <IP>.8001    130880      0 139264      0 CLOSE_WAIT 
<IP>.45899   <IP>.8001    130880      0 139264      0 CLOSE_WAIT 

5. After 30 seconds, the TCP scoket is still in CLOSE_WAIT and is still not cleared out.

The CLOSE_WAIT state is temporary and should only remain for a split second, between the first FIN and the last ACK, but remains forever.

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
Changes
Cause
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.