11-20-2009
Thanks for the reply jlliagre,
Due the application urgency we are forced to go for the application (weblogic server restart to kill the connections ) then the connection status went to FIN_WAIT_1 from ESTABLISHED and later on it dissappered. Now BAU.
But the appplication bug is there so we may need to find out other than the application restart.
I followed the way you shown and i have find out the process but again it was the weblogic server running on the system. which means in order to kill the connection i need to kill/stop the weblogic server
'
But any way great learning !!
Thanks again for your patience in explaining this
Cheers
GIC
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi Experts,
need help about release or refresh TCP Connection:
i have the sample like below :
application log connection:
0500 ( 192.168.0.1:36053) 00919 2007/05/10 23:30:25 112 13 2007/05/10 23:30:25 1969/12/31 17:00:00
0500 ( 192.168.0.1:36054) 00920 2007/05/10 23:30:26 000 00... (3 Replies)
Discussion started by: bucci
3 Replies
2. UNIX for Dummies Questions & Answers
I wrote a very simple script to calculate the DB connection from an appserver and check the total netstat connection to a particular DB exceed 25 then it will send mail
netstat -a 2> /dev/null | awk '/.*ESTAB/{print $5}' | cut -d. -f1 | uniq -c | awk '{if ($1 > 25)print $2," exceed ",$1;}'
... (1 Reply)
Discussion started by: senthil.ak
1 Replies
3. Red Hat
How to kill all active tcp connections from an IP?
I am using CentOS (3 Replies)
Discussion started by: an00p
3 Replies
4. UNIX for Advanced & Expert Users
Hi - I frequently run commands, and transfer files to/from a host that uses SecurID ssh authentication. It is a real pain to have to enter the authentication information every time I want to interact with this host. I am wondering if there is a way to establish a one-time ssh connection to this... (2 Replies)
Discussion started by: cpp6f
2 Replies
5. UNIX for Dummies Questions & Answers
Dear experts,
I am seeing a lot of TCP failed connection attempts from "netstat -s" on one of our servers.
How can I pin point what connection failed and what are the ports involved?
Any tools/commands I can dig in deeper to diag. what went wrong on these "failed connection attempts"?
... (2 Replies)
Discussion started by: cache51
2 Replies
6. Shell Programming and Scripting
HI
I know that it sounds crazy :eek:
appreciated if any one provided me a solution for my below case , the below script is checking the Database availability on many servers by establishing rsh session ( one by one ) , sometime one of the servers goes down and while this the script taking... (0 Replies)
Discussion started by: bejo4ever
0 Replies
7. Red Hat
Hi,
I want to kill TCP connections which have status as TIME_WAIT & no PID
(as per the output of the "netstat - p" command).
Is there any command/utility available to kill connections to a specific port or IP address.
The problem is that these connections don't have process ID (see... (4 Replies)
Discussion started by: Davinder31may
4 Replies
8. IP Networking
Hello
netstat -p give below 6634176 connections as closed.How do we trace that which all connections are being closed on the server?
1366888371 data packet headers correctly predicted
1195906 connection requests
5227320 connection accepts
5992919... (6 Replies)
Discussion started by: Vishal_dba
6 Replies
9. AIX
I'm trying to configure a firewall for AIX to accept incoming connections on ports 22 and 443 and deny everything else. All is ok; the server accepts connections only on 22 and 443, but after that I also need to accept all outgoing connections -- ssh and telnet, for example. So I started with
... (0 Replies)
Discussion started by: Michael1457
0 Replies
10. UNIX for Advanced & Expert Users
Good morning, I need your help please
After Restarting Aps or connection, these are connections
tcp 0 0 10.80.1.26.57597 10.81.248.79.53008 ESTABLISHED
tcp 0 47 10.80.1.26.57607 10.81.248.79.53008 ESTABLISHED
tcp 0 0 ... (4 Replies)
Discussion started by: alexcol
4 Replies
XKILL(1) General Commands Manual XKILL(1)
NAME
xkill - kill a client by its X resource
SYNOPSIS
xkill [-display displayname] [-id resource] [-button number] [-frame] [-all]
DESCRIPTION
Xkill is a utility for forcing the X server to close connections to clients. This program is very dangerous, but is useful for aborting
programs that have displayed undesired windows on a user's screen. If no resource identifier is given with -id, xkill will display a spe-
cial cursor as a prompt for the user to select a window to be killed. If a pointer button is pressed over a non-root window, the server
will close its connection to the client that created the window.
OPTIONS
-display displayname
This option specifies the name of the X server to contact.
-id resource
This option specifies the X identifier for the resource whose creator is to be aborted. If no resource is specified, xkill will
display a special cursor with which you should select a window to be kill.
-button number
This option specifies the number of pointer button that should be used in selecting a window to kill. If the word "any" is speci-
fied, any button on the pointer may be used. By default, the first button in the pointer map (which is usually the leftmost but-
ton) is used.
-all This option indicates that all clients with top-level windows on the screen should be killed. Xkill will ask you to select the
root window with each of the currently defined buttons to give you several chances to abort. Use of this option is highly discour-
aged.
-frame This option indicates that xkill should ignore the standard conventions for finding top-level client windows (which are typically
nested inside a window manager window), and simply believe that you want to kill direct children of the root.
CAVEATS
This command does not provide any warranty that the application whose connection to the X server is closed will abort nicely, or even abort
at all. All this command does is to close the connection to the X server. Many existing applications do indeed abort when their connection
to the X server is closed, but some can choose to continue.
XDEFAULTS
Button Specifies a specific pointer button number or the word "any" to use when selecting windows.
SEE ALSO
X(7), xwininfo(1), XKillClient and XGetPointerMapping in the Xlib Programmers Manual, KillClient in the X Protocol Specification
AUTHOR
Jim Fulton, MIT X Consortium
Dana Chee, Bellcore
X Version 11 xkill 1.0.3 XKILL(1)