Sponsored Content
Operating Systems Linux Red Hat Too many CLOSE_WAIT connections Post 302564687 by Duffs22 on Friday 14th of October 2011 10:34:46 AM
Old 10-14-2011
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.
 

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

clear CLOSE_WAIT status

Hi, I have an application with a bug in it that keeps sockets in CLOSE_WAIT, which eventually freezes the server because the user account it runs under runs out of file handles. We have the bug fixed but can only release the fix with the next release. Does anyone know how I can clear the... (3 Replies)
Discussion started by: rein
3 Replies

3. 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

4. UNIX for Dummies Questions & Answers

Hitting with custom port in CLOSE_WAIT state for long time in solaris 10

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... (0 Replies)
Discussion started by: mgmk.84
0 Replies

5. 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

6. 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

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

8. 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

9. 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

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
Jifty::Script::Server(3pm)				User Contributed Perl Documentation				Jifty::Script::Server(3pm)

NAME
Jifty::Script::Server - A standalone webserver for your Jifty application SYNOPSIS
jifty server jifty server --port 6666 jifty server --stop DESCRIPTION
Starts and stops Jifty's standalone web server. options --port The port to run the server on. Overrides the port in the config file, if it is set there. The default port is 8888. --user USER The user to become after binding to the port. It is advised that you use this when binding to low ports, instead of running as "root". This option only works if the server is using a Net::Server subclass. --group GROUP The group to become after binding to the port. Like "--user", this option only works if the server is using a Net::Server subclass. --host HOSTNAME The host to bind to. This option only works if the server is using a Net::Server subclass. --stop Stops the server, if it is running. This is accomplished by reading the PID from "var/jifty-server.pid" --restart restart the server, if it is running. This is accomplished by killing the child pid, and let parent pid create a new one --sigready SIGNAL Sets the signal number that should be sent to the server's parent process when the server is ready to accept connections. --quiet Reduces the amount of debug output sent by the server --dbiprof Turns on DBI profiling; see DBI::ProfileDumper. --help Print a brief help message and exits. --man Prints the manual page and exits. DESCRIPTION
When you're getting started with Jifty, this is the server you want. It's lightweight and easy to work with. METHODS
run "run" takes no arguments, but starts up a Jifty server process for you. perl v5.14.2 2010-12-08 Jifty::Script::Server(3pm)
All times are GMT -4. The time now is 06:43 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy