Sponsored Content
Full Discussion: clear CLOSE_WAIT status
Top Forums UNIX for Advanced & Expert Users clear CLOSE_WAIT status Post 302091894 by rein on Thursday 5th of October 2006 04:50:10 PM
Old 10-05-2006
I know the problem is in our code and we have a fix for it but we can't role it out immediately in a production environment. Clearing the CLOSE_WAIT is just an emergency solution, and better then restarting the application servers daily.

We're planning a new release tomorrow that should fix the problem.

The fix is using a multithreaded connection pool instead of openening a new connection per request which in case of a probable memory leak causes the socket to stay occupied while being in CLOSE_WAIT.
 

10 More Discussions You Might Find Interesting

1. Solaris

remove CLOSE_WAIT connections

Hi folks. I have a problem that I need to remove CLOSE_WAIT connections. On AIX version 5.x, I can use rmsock command. Is there a similar command on Solaris ? Is there an other solution for this situation ? Thanks. (6 Replies)
Discussion started by: Livio
6 Replies

2. UNIX for Advanced & Expert Users

close_wait connections causing a server to hung

Hi Guys, Just wondering if anyone of you have been in a situation where you end up having around 100 close_wait connections and seems to me those connections are locking up resources/processes in the server so unless the server is rebooted those processes won't be released by the close_wait... (3 Replies)
Discussion started by: hariza
3 Replies

3. Solaris

CLOSE_WAIT problem in solaris server

Hi, Occasionally I am getting the port state in CLOSE_WAIT for long time in the solaris server. I am not sure is it application problem or not. Because we are using port 9009 for Tomcat process in our web application, some time when I start the application, the port 9009 is in CLOSE_WAIT... (2 Replies)
Discussion started by: mgmk.84
2 Replies

4. Solaris

How to remove CLOSE_WAIT in Solaris

Hi, We are using a application which uses port in CLOSE_WAIT Status. netstat -an|grep 9191 192.168.32.11.9191 192.168.32.11.54562 49152 0 49152 0 CLOSE_WAIT 192.168.32.11.9191 192.168.32.11.54564 49152 0 49152 0 CLOSE_WAIT 192.168.32.11.9191 192.168.32.11.54568 ... (2 Replies)
Discussion started by: helplineinc
2 Replies

5. Red Hat

Too many CLOSE_WAIT connections

Hi, I am running JBOSS 6 ona RHEL5 server put it continuously crashes due to the number of CLOSE_WAIT connections on port 8080. How can I kill the several hundred CLOSE_WAIT connections without killing the actual live "LISTENING" connection? R, D. (2 Replies)
Discussion started by: Duffs22
2 Replies

6. UNIX for Advanced & Expert Users

stuck in CLOSE_WAIT Solaris 10 - Patch and workaround

Solaris 10 Sparc: When you got a connection locking a tcp/port, and the status is CLOSE_WAIT (for ever :wall:), you just use the tcpdrop, to close the connection. This is a OS bug. I wrote the bug id bellow: BUG-ID 6468753 connections stuck in CLOSE_WAIT The patch that's correct the bug:... (0 Replies)
Discussion started by: thiagofborn
0 Replies

7. Shell Programming and Scripting

Terminate processes for CLOSE_WAIT status of TCP

Hello Friends, First of all im sorry for spending extra space in DB of forum with this thread, i know there would be a solution if i kept searching, I need to terminate the process which causes CLOSE_WAIT status of TCP connection via port 8103: -bash-3.00$ netstat -na | grep 8103... (3 Replies)
Discussion started by: EAGL€
3 Replies

8. AIX

How to repair a TCP/IP socket in state: CLOSE_WAIT?

Hi The clients connect to my server -using port 9130. But no client could connect to my server at this time. I've checked already and this is the result netstat -Aan|grep -v 127.0.0.1|grep 9130|pg f10006000abcb398 tcp4 10313 0 10.0.89.81.9130 10.158.70.24.1705 CLOSE_WAIT... (8 Replies)
Discussion started by: bobochacha29
8 Replies

9. Shell Programming and Scripting

Clear contents of specified directories, then return exit status

Hello, this is my first post here. I'm attempting to write a bash shell script to rm the contents of a directory without deleting the directory, specifically in OS X 10.10 . Here's what I have: function clear() { USER="$USER" DIR=$1 rm -rfv /Users/"$USER"/library/$DIR/* } clear... (6 Replies)
Discussion started by: YouNicks
6 Replies

10. Solaris

How to remove CLOSE_WAIT in Solaris 5.10?

Hi, We are using a application which uses port in CLOSE_WAIT Status. netstat -an|grep 9191 192.168.32.11.9191 192.168.32.11.54562 49152 0 49152 0 CLOSE_WAIT 192.168.32.11.9191 192.168.32.11.54564 49152 0 49152 0 CLOSE_WAIT 192.168.32.11.9191 192.168.32.11.54568 49152 0 49152 0 CLOSE_WAIT... (5 Replies)
Discussion started by: SHIV&JYOTI
5 Replies
tcprules(1)						      General Commands Manual						       tcprules(1)

NAME
tcprules - compile rules for tcpserver SYNOPSIS
tcprules rules.cdb rules.tmp OVERVIEW
tcpserver optionally follows rules to decide whether a TCP connection is acceptable. For example, a rule of 18.23.0.32:deny prohibits connections from IP address 18.23.0.32. tcprules reads rules from its standard input and writes them into rules.cdb in a binary format suited for quick access by tcpserver. tcprules can be used while tcpserver is running: it ensures that rules.cdb is updated atomically. It does this by first writing the rules to rules.tmp and then moving rules.tmp on top of rules.cdb. If rules.tmp already exists, it is destroyed. The directories containing rules.cdb and rules.tmp must be writable to tcprules; they must also be on the same filesystem. If there is a problem with the input, tcprules complains and leaves rules.cdb alone. The binary rules.cdb format is portable across machines. RULE FORMAT
A rule takes up one line. A file containing rules may also contain comments: lines beginning with # are ignored. Each rule contains an address, a colon, and a list of instructions, with no extra spaces. When tcpserver receives a connection from that address, it follows the instructions. ADDRESSES
tcpserver starts by looking for a rule with address TCPREMOTEINFO@TCPREMOTEIP. If it doesn't find one, or if TCPREMOTEINFO is not set, it tries the address TCPREMOTEIP. If that doesn't work, it tries shorter and shorter prefixes of TCPREMOTEIP ending with a dot. If none of them work, it tries the empty string. For example, here are some rules: joe@127.0.0.1:first 18.23.0.32:second 127.:third :fourth ::1:fifth If TCPREMOTEIP is 10.119.75.38, tcpserver will follow the fourth instructions. If TCPREMOTEIP is ::1, tcpserver will follow the fifth instructions. Note that you cannot detect IPv4 mapped addresses by matching "::ffff", as those addresses will be converted to IPv4 before looking at the rules. If TCPREMOTEIP is 18.23.0.32, tcpserver will follow the second instructions. If TCPREMOTEINFO is bill and TCPREMOTEIP is 127.0.0.1, tcpserver will follow the third instructions. If TCPREMOTEINFO is joe and TCPREMOTEIP is 127.0.0.1, tcpserver will follow the first instructions. ADDRESS RANGES
tcprules treats 1.2.3.37-53:ins as an abbreviation for the rules 1.2.3.37:ins, 1.2.3.38:ins, and so on up through 1.2.3.53:ins. Similarly, 10.2-3.:ins is an abbreviation for 10.2.:ins and 10.3.:ins. INSTRUCTIONS
The instructions in a rule must begin with either allow or deny. deny tells tcpserver to drop the connection without running anything. For example, the rule :deny tells tcpserver to drop all connections that aren't handled by more specific rules. The instructions may continue with some environment variables, in the format ,VAR="VALUE". tcpserver adds VAR=VALUE to the current envi- ronment. For example, 10.0.:allow,RELAYCLIENT="@fix.me" adds RELAYCLIENT=@fix.me to the environment. The quotes here may be replaced by any repeated character: 10.0.:allow,RELAYCLIENT=/@fix.me/ Any number of variables may be listed: 127.0.0.1:allow,RELAYCLIENT="",TCPLOCALHOST="movie.edu" SEE ALSO
tcprulescheck(1), tcpserver(1), tcp-environ(5) tcprules(1)
All times are GMT -4. The time now is 10:06 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy