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
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
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
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
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
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
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
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
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
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
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
LEARN ABOUT SUNOS
delete-jdbc-connection-pool
asadmin-delete-jdbc-connection-pool(1AS) User Commands asadmin-delete-jdbc-connection-pool(1AS)
NAME
delete-jdbc-connection-pool - removes the JDBC connection pool
SYNOPSIS
delete-jdbc-connection-pool --user admin_user [--password admin_password] [--host localhost] [--port 4848] [--secure|-s] [--passwordfile
filename] [--terse=false] [--echo=false] [--interactive] [--cascade=false] connection_pool_ID
Removes the JDBC connection pool. This command is supported in remote mode only.
OPTIONS
--user authorized domain application server administrative username.
--password password to administer the domain application server.
--host machine name where the domain application server is running.
--port port number of the domain application server listening for administration requests.
--secure if true, uses SSL/TLS to communicate with the domain application server.
--passwordfile file containing the domain application server password.
--terse indicates that any output data must be very concise, typically avoiding human-friendly sentences and favoring well-
formatted data for consumption by a script.
--echo setting to true will echo the command line statement on the standard output.
--interactive prompts you for the required options that are not already specified.
--cascade If set to true, deletes all the connector resources associated with the pool, apart from the pool itself. If set to
false (default), the deletion of the pool fails if there are any resources associated with the pool. Either the
resource has to be deleted explicitly, or set the option to true.
OPERANDS
connection_pool_id name of the JDBC connection pool to be deleted.
Example 1: Using the delete-jdbc-connection-pool command
asadmin> delete-jdbc-connection-pool --user admin
--password adminadmin --host fuyako port 7070 XA_connection_pool
Deleted the JDBC connection pool resource with id = XA_connection_pool
Where: the XA_connection_pool resource is deleted.
EXIT STATUS
0 command executed successfully
1 error in executing the command
asadmin-create-jdbc-connection-pool(1AS), asadmin-list-jdbc-connection-pools(1AS)
J2EE 1.4 SDK March 2004 asadmin-delete-jdbc-connection-pool(1AS)