CLOSE_WAIT Problem.
Hi,
The following is among the list of fixes in Weblogic 4.5.1.
" CR 37789: Sockets on the server were opened by the web server and then closed.
But they still were stuck in the CLOSE_WAIT state on the server. Eventually all
these sockets took up all the file descriptors available and the server hanged--
unable to answer requests. This has been fixed."
We are using Weblogic 6.1 sp2 with aix 433. But we still have the above problem.
How do we handle this?
Regs
Vaidy
Fixed in Weblogic 6.1 sp 2
044988 Fixed a problem with the NSAPI plug-ins where the socket was not properly closed by the plugin side. The un-closed socket on the webserver side will be left in CLOSE_WAIT state.
Greg Schuler wrote:
We are using WebLogic 6.0 SP2 on Solaris 7 and we have a similar problem. A sudden burst of traffic will cause a large build-up of CLOSE_WAIT connections on the WebLogic server, and meanwhile on the Apache web serve we see lots of the following messages in the error_log file:
[Mon Mar 18 14:39:57 2002] [error] READ_TIMEOUT [os error=0, line 485 of ap_proxy.cpp]:
Seems like a WebLogic/Apache plug-in problem.
Note: we've tried using Netscape/iPlanet on the web tier, and that results in a build up of the CLOSE_WAITs on the web tier instead of the app tier. Very strange....
Any ideas?
Thanks,
/Greg
Similar Messages
-
CLOSE_WAIT problems with Oracle 9iAS on Solaris
All,
We have some simple JSP + Sevlets running on Oracle 9iAS on a Solaris server. After the App Server has been running for a couple of minutes we start to get several TCP connections with a CLOSE_WAIT status - as shown by a netstat output.
These seem to be a result of a FIN_WAIT_2 and CLOSE_WAIT pairing eg
Local Remote Swind Send-Q Rwind Recv-Q Status
SERVER.43009 SERVER.80 49152 0 49152 0 CLOSE_WAIT
SERVER.80 SERVER.43009 49152 0 49152 0 FIN_WAIT_2
Over time the FIN_WAIT_2 is removed, leaving the CLOSE_WAITs.
Has anyone else had this problem?
KeithWe're having similar problem. We have lot's of close_wait between Apache and OC4J.
Swetal -
Hi Everyone,
I can see this has been posted several times before but hear me out. I am very knew to WebLogic, Unix, Apache etc....
We are suffering with this close_wait problem in all of our environments. I honestly do know if it is even a WebLogic problem, it seems to be the general consensus amongst everyone here. I have taken on the support and maintenance of the WebLogic infrastructure not including the underlying oracle databases. from the DBA team. They do not seem to know where the close_wait issue is coming from and neither do I.
From what I understand (correct me if I am wrong) is that either the client or the OS (which OS I have no idea) is not closing the socket after it has finished.
The situation is that at some point during a day, lets say our development WebLogic environment will stop responding. The deployed application will stop working and I will be unable to log in to the WebLogic Admin Console which in turn prevents me from viewing any of the managed servers which in turn results in the Unix team bouncing the LPAR. I then have to bring up the WebLogic environment. I'm told that an LPAR should never need bouncing!
If I run various nestat commands to identify close_wait while we have the above problem, it can report as many as 300 close_waits or only maybe 12 - it is very random! It would appear that it doesnt matter how many close-waits there are which makes me think, are close_wait the real problem.
Can close_waits consume the servers resources so much it buggers the system?
I'd really appreciate some advice as to where to start with this.
I look forward to your replies.
Thanks,
CraigTo control resource usage, the OS (in your case AIX) restricts the number of open file descriptors (TCP sockets related to HTTP connections of your server) per process.
All TCP connections that have been closed will go into TIME_WAIT state. While in TIME_WAIT state, the OS maintains the resources allocated to the socket.
As a result, busy server processes can fill-up the server process file descriptor. To deal with this problem you need to tune your OS (in this case AIX)
First we want to measure the number of sockets in TIME_WAIT state,
netstat -a | grep TIME_WAIT | wc -lThis command will count all of the TCP connections that are in the TIME_WAIT state. As this number
approaches the maximum number of file descriptors per process, your application's throughput will
suffer dramatic degradations because new connection requests may have to wait for a free space in the
application’s file descriptor table.
On AIX you can use the no command to display all network attributes.
With no -o tcp_timewait=<interval> the time a socket stays in TIME_WAIT can be adjusted (Note that the time is 'interval * 15' seconds).
AIX uses a listen queue with a fixed size (1024) on busy servers you might want to increase the size (use the parameters somaxconn)
In the WebLogic server you have to adjust Accept BackLog (in the console use the tuning, configuration tab of the server).
This only a first step, you can also tune the server (work managers, Java virtual machine etcetera). But for this you need a lot more input. -
hello all,
hereby, I am newbie in nokia software updater. I am user of nokia n70. here some information about my phone :
Nokia N70-1
V 2.0536.0.2
12-09-05
RM-84
code : 0524118
the problem is, my nsu hang at starting application, I tried to wait almost 4 hours, but nothing good happen. I check at my netstat. it shown that www.dsut.online.nokia.com:https close_wait. i tried many of tips given by this forum but not worked. I really hope that some one can help me to solve my problem. thanks.yeah no solution, you and me are only few of thousands with this problem worldwide...seems like nokia doesn't care about us. A shame that one of the biggest Names in Mobile Industrie can't programm a little good working software like the other big Brands in that business.
-
"Failed to Send the HTTP Message..." - HTTPSupport problem
Hello,
We're having a few difficulties when the HTTPServer in UDS5.0.3 running on Solaris 8. Basically, we have a pair of MS .NET servers using some XML Webservices that we reside on the UDS server.
The symptoms of the problem are that a lot of "Failed to send the HTTP message..." messages are being seen in the log for the partition that contains instances of the HTTPServer. The reason given is a UsageException on the ExternalConnection - stating that the "Object is not open for I/O so it cannot be read or written" (ExternalConnection::Write at 1). This only occurs when a HTTP Response is to be sent back to the .NET server.
Unfortunately, this exception appears to be occurring somewhere within the code held in the HTTPSupport library, so we can't easily trace the error. Worse still, we don't actually know what's causing the error.
Does the error indicate a problem with comms between our UDS HTTPServer and the .NET servers? We've also noticed a large number of socket connections being left in a state of CLOSE_WAIT when this error occurs (which eventually block the port altogether resulting in the HTTPServer instances becoming unresponsive).
As far as I can tell, the Solaris TCP/IP settings are all at the OS default.
Many thanks for any assistance,
Jason Bridgen.Hi Gordon,
The problem was solved, the customer changed his ip adress on the server and it's OK now!
Thank you !!
Hilla. -
TCP Socket connection in CLOSE_WAIT status and not getting closed
I am facing an issue with the TCP socket connections not getting closed and they are in CLOSE_WAIT status for ever.
As a part of batch process in our application, emails are sent with 4 embedded images. These images are downloaded from 3rd party site with IP say "UUU.XXX.YYY.ZZZ"
The images are embedded to email as follows
1. An URL object is created with the site url.
URL urlPhoto = new
URL("http://UUU.XXX.YYY.ZZZ/email/photos.jpg");
2. The image cid is created with the URL object and the image name
HtmlEmail htmlEmail = new HtmlEmail();
String cid1 = htmlEmail.embed(urlPhoto,
"photo.jpg");
3. The image cid is added to the email template by replacing the ${cid1} and the email is sent.
<td valign="top">
<img src="cid:${cid1}" width="279" height="274">
</td>
When a mail is sent, 4 new TCP connections are opened and are put in CLOSE_WAIT status for ever. For every mail sent 4 new connections are opened. In UNIX there is an upper limit on the number of open file handles (defaults to 1024) at any point of time. The open TCP connection has the underlying socket in CLOSE_WAIT status and is not getting closed at all. When the upper limit (1024) is reached the batch process is throwing the following exception and terminates.
Caused by: com.inet.tds.ap: java.net.SocketExceptionjava.net.SocketException: Too many open files
at com.inet.tds.am.a(Unknown Source)
at com.inet.tds.TdsDriver.a(Unknown Source)
at com.inet.tds.TdsDriver.connect(Unknown Source)
at java.sql.DriverManager.getConnection(DriverManager.java:525)
at java.sql.DriverManager.getConnection(DriverManager.java:171)
at com.hcomemea.batchprocess.dataaccess.database.BaseJdbcDao.openConnection(BaseJdbcDao.java:106)
... 12 more
When I run the command lsof in UNIX which list the open file handles in the system
$ /usr/sbin/lsof -p 22933 -i | grep CLOSE_WAIT
java 22933 build_master 297u IPv6 129841943 TCP integration.com:47929->UUU.XXX.YYY.ZZZ:http (CLOSE_WAIT)
java 22933 build_master 298u IPv6 129841947 TCP integration.com:47933->UUU.XXX.YYY.ZZZ:http (CLOSE_WAIT)
java 22933 build_master 299u IPv6 129841950 TCP integration.com:47936->UUU.XXX.YYY.ZZZ:http (CLOSE_WAIT)
java 22933 build_master 300u IPv6 129841970 TCP integration.com:47952->UUU.XXX.YYY.ZZZ:http (CLOSE_WAIT)
���list of 935 connections similarly�
I tried 2 solutions
1. Got the HttpURLConnection from the URL object and invoked disconnect method on the same. But it doesn�t work.
2. Ran the batch process java program with the parameter �Dhttp.keepAlive=false to close the underlying connection but didn�t help.
I need the underlying sockets to be closed and not put in CLOSE_WAIT status after sending the mail.
Is it the problem with the embed method of HtmlEmail object not closing the underlying socket connection.
If anyone has faced this issue before, kindly let me know the possible solutions for the same ASAP.
Thank you,
Ramesh GThis sounds more like a problem due to connection pooling at middle tier/application server.
If that has been ruled out, then you might to enable DCD or set expiry time on the server. -
Can't run form from Form Builder 10g - Port configuration problem?
Hi,
I have installed the Database (10.2.0.1.0) and the Developer Suite (10.1.2.0.2) on two Linux machines (Red Hat Enterprise Linux ES 4 Basic).
If I enter the frmservlet-URL manually everything seems to be fine.
In one case I enter http://127.0.0.1:8890/forms/frmservlet, in the other http://127.0.0.1:8889/forms/frmservlet; in BOTH cases I get eventually a dark square and the status bar says "Applet oracle.forms.engine.Main started".
HOWEVER, if I create a simple form with Form Builder and click on the Button with the green traffic light ("Run Form"), the form runs only on the machine where frmservlet listens on port 8890.
On the other machine (frmservlet configured to listen on port 8889) Firefox pops up, the URL "http://127.0.0.1:32979/6dOrpwghCqnp8PhMT7KVT533m3IaArqFbPqPBOztZXWYSsNy" gets called, and nothing else happens. The screen displays the string "ORACLE FORMS." and the status bar says "Waiting for 127.0.0.1...", and it stays like this forever.
I assume this is a port configuration problem, but I don't have a clue where to start.
Any suggestions how I should proceed are greatly appreciated.
Thank you very much in advance!Hi Frank,
Thank you for your reply.
I doublechecked my configuration.
In the dialog Edit --> Preferences --> Runtime the Application Server URL is set to "127.0.0.1:8889/forms/frmservlet".
However, when I attempt to run the form, the URL "http://127.0.0.1:33140/W2dwbV9eXS2fPkuKlxNhCxFWdEihwDviat2uV7ycrSotqwDN" gets called.
The screen displays the string "ORACLE FORMS." and the status bar says "Waiting for 127.0.0.1...", and that's it.
I wonder how the port number 33140 got selected. Interestingly, this time it is a different number; last time it was port 32979. In fact, the port number seems to change each time; I tried again and now it is 33189.
I will now try to set the port number for the frmservlet to 8890.
I choose Edit --> Preferences --> Runtime and set the application server URL to "127.0.0.1:8890/forms/frmservlet".
I stop the container, open /home/oracle/OraHome_1/j2ee/DevSuite/config/default-web-site.xml and change the port number to 8890:
<?xml version="1.0" standalone='yes'?>
<!DOCTYPE web-site PUBLIC "Oracle Application Server 10g XML Web-site" "http://xmlns.oracle.com/ias/dtds/web-site.dtd">
<!-- change the host name below to your own host name. Localhost will -->
<!-- not work with clustering -->
<!-- also add cluster-island attribute as below
<web-site host="localhost" port="0" protocol="ajp13"
display-name="Default Oracle Application Server 10g Java WebSite" cluster-island="1" >
-->
<web-site port="8890" protocol="http"
display-name="Oracle Developer Suite 10g instance of Oracle Containers for J2EE Web Site">
<!-- Uncomment the following line when using clustering -->
<!-- <frontend host="your_host_name" port="80" /> -->
<!-- The default web-app for this site, bound to the root -->
<default-web-app application="default" name="defaultWebApp" root="/j2ee" />
<!-- Do not delete this line. -->
<web-app application="forms" name="formsweb" root="/forms" />
<!-- -->
<!-- <web-app application="forms" name="formsweb" root="/forms" /> -->
<web-app application ="reports" name="web" root="/reports" />
<web-app application = "reports" name="demo" root="/repdemo" />
<!-- Access Log, where requests are logged to -->
<access-log path="../log/default-web-access.log" />
</web-site>
I restart the container, start Form Builder, connect to the database, and open my test form.
When attempting to run the form, the URL "http://127.0.0.1:33437/Pl0n3ky9vmU5z37A7ScBnQhsGwq3jwuzJpgTAKWPMOYIzT8K" gets called (again a new port number, apparently picked radomly within a certain range) and nothing happens: "Waiting for 127.0.0.1...".
However, when I enter the URL http://127.0.0.1:8890/forms/frmservlet I do (eventually, after confirming that I trust the certificate etc.) get a darc rectangle and the status message "Applet oracle.forms.engine.Main started", which tells me that my setup can't be that far off target.
Here is the output of netstat:
[root@localhost ~]# netstat -anp --tcp
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:32769 0.0.0.0:* LISTEN 2779/rpc.statd
tcp 0 0 0.0.0.0:23910 0.0.0.0:* LISTEN 5269/java
tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 2759/portmap
tcp 0 0 0.0.0.0:1521 0.0.0.0:* LISTEN 4265/tnslsnr
tcp 0 0 0.0.0.0:113 0.0.0.0:* LISTEN 2983/xinetd
tcp 0 0 127.0.0.1:7830 0.0.0.0:* LISTEN 4429/spamd --port 7
tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 2928/cupsd
tcp 0 0 0.0.0.0:9240 0.0.0.0:* LISTEN 5269/java
tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN 3002/sendmail: acce
tcp 0 0 0.0.0.0:8890 0.0.0.0:* LISTEN 5269/java
tcp 0 0 0.0.0.0:32795 0.0.0.0:* LISTEN 4231/ora_d000_orcl
tcp 0 0 127.0.0.1:1521 127.0.0.1:32817 ESTABLISHED 4265/tnslsnr
tcp 0 0 127.0.0.1:32817 127.0.0.1:1521 ESTABLISHED 4209/ora_pmon_orcl
tcp 0 0 127.0.0.1:33425 127.0.0.1:1521 ESTABLISHED 5298/frmbld
tcp 0 0 127.0.0.1:1521 127.0.0.1:33425 ESTABLISHED 5311/oracleorcl
tcp 1 0 80.133.127.83:33485 209.132.177.100:443 CLOSE_WAIT 4060/python
tcp 1 0 80.133.127.83:33484 209.132.177.100:443 CLOSE_WAIT 4060/python
tcp 1 0 80.133.127.83:33494 209.132.177.100:443 CLOSE_WAIT 4060/python
tcp 1 0 80.133.127.83:33520 209.132.177.100:443 CLOSE_WAIT 4060/python
tcp 0 0 80.133.127.83:33529 209.132.177.100:443 ESTABLISHED 4060/python
tcp 0 0 80.133.127.83:33528 209.132.177.100:443 ESTABLISHED 4060/python
tcp 1 0 80.133.127.83:33460 209.132.177.100:443 CLOSE_WAIT 4060/python
tcp 1 0 80.133.127.83:33470 209.132.177.100:443 CLOSE_WAIT 4060/python
tcp 0 0 :::22 :::* LISTEN 2968/sshd
tcp 0 0 ::ffff:127.0.0.1:33437 :::* LISTEN 5298/frmbld
tcp 697 0 ::ffff:127.0.0.1:33437 ::ffff:127.0.0.1:33439 CLOSE_WAIT -
tcp 348 0 ::ffff:127.0.0.1:33437 ::ffff:127.0.0.1:33440 CLOSE_WAIT -
[root@localhost ~]#
The question remains: Where do those port numbers come from?
Regards,
jme -
Hey,
I'm writing a simple client/server app and I'm trying to test it on my local machine. Every time I try to connect to the server I get a ConnectException. I'm running Ubuntu Intrepid (which I suspect may have something to do with my problem).
This is how I'm setting up the server (just to add, this is threaded):
this.socket = new ServerSocket(TCP_SERVER_PORT);
socket.accept(); //blah, blah, blahAnd this is how I'm trying to connect:
this.socket = new Socket("127.0.0.1",TCP_SERVER_PORT);I have no idea why this fails! Any ideas?
Cheers,
Puffejp wrote:
I get a ConnectExceptionwith what message?I get:
java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:519)
at java.net.Socket.connect(Socket.java:469)
at java.net.Socket.<init>(Socket.java:366)
at java.net.Socket.<init>(Socket.java:180)
at client.TCPClient.<init>(TCPClient.java:30)
at client.TCPClient.main(TCPClient.java:74)
socket.accept(); //blah, blah, blahYou mean Socket client = socket.accept();That is what I mean, sorry (lazyness! :)).
And this is how I'm trying to connect:
this.socket = new Socket("127.0.0.1",TCP_SERVER_PORT);
That should certainly work on the host the server is running on. Could be your /etc/hosts file. It should map 'localhost' to 127.0.0.1, and your real hostname to your real IP address. This is a common, and rather shocking, problem with some Linux distributions.
127.0.0.1 localhost
127.0.1.1 peter-laptop
# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
Also can you post the output of netstat -na after you have started the server.
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN
tcp 1 1 192.168.1.70:57052 72.5.124.102:80 LAST_ACK
tcp 1 0 192.168.1.70:38987 66.102.9.100:80 CLOSE_WAIT
tcp 1 1 192.168.1.70:57047 72.5.124.102:80 LAST_ACK
tcp 1 1 192.168.1.70:57049 72.5.124.102:80 LAST_ACK
tcp 1 1 192.168.1.70:57051 72.5.124.102:80 LAST_ACK
tcp 1 1 192.168.1.70:57050 72.5.124.102:80 LAST_ACK
tcp 1 1 192.168.1.70:57048 72.5.124.102:80 LAST_ACK
tcp6 0 0 :::22 :::* LISTEN
udp 0 0 0.0.0.0:41091 0.0.0.0:*
udp 0 0 0.0.0.0:68 0.0.0.0:*
udp 0 0 0.0.0.0:5353 0.0.0.0:* I've cut out the bit after "Active UNIX domain sockets" because the message was too long, but I have it if it would help.
Does this shed any light on the problem?
Cheers,
Pete
Edited by: Puffy on Jan 9, 2009 10:48 AM -
Facing problem while adding combobox using gridbaglayout
HI, I have used gridbaglayout in my panel. after adding the gridbaglayout, if i select long value combobox does't display all the value of the selected value. Why?
This is my code
cboPrioritySearchValue = new JComboBox();
cboPrioritySearchValue.setBackground(Color.white);
cboPrioritySearchValue.addItem("ALL");
cboPrioritySearchValue.addItem(Priority.NOT.getValue());
cboPrioritySearchValue.addItem(Priority.ONE.getValue());
cboPrioritySearchValue.addItem(Priority.TWO.getValue());
cboPrioritySearchValue.addItem(Priority.THREE.getValue());
cboPrioritySearchValue.addItem(Priority.FOUR.getValue());
setConstraints(gbc,gbc.WEST,gbc.NONE,2,1,2,8,new Insets(2,5,5,5),0,0,0,0);
gbl.setConstraints(cboPrioritySearchValue,gbc);
panel.add(cboPrioritySearchValue);This is my setConstraints method,
public GridBagConstraints setConstraints(GridBagConstraints gbc, int anchor,int fill,
int gridw, int gridh, int gridx, int gridy,
Insets insets, int ipadx, int ipady,
int weightx, int weighty)
gbc.anchor = anchor;
gbc.fill = fill;
gbc.gridwidth = gridw;
gbc.gridheight = gridh;
gbc.gridx = gridx;
gbc.gridy = gridy;
gbc.insets = insets;
gbc.ipadx = ipadx;
gbc.ipady = ipady;
gbc.weightx = weightx;
gbc.weighty = weighty;
return gbc;
}Edited by: JavaHeroPrince on May 13, 2010 6:58 AMThanks Pete, hopefully its only a temporary problem.Short answer: It is (well ... hopefully).
Long answer: My server's dying regularly because all the connections fill up in CLOSE_WAIT states. This doesn't seem to have the same root cause as the reported bugs that I can find (issues with older JDKs) so I'm interested in investigating it beyond just upgrading everything to the latest and crossing my fingers. Unfortunately that will take time and I'm a bit pressed for spare time at the moment - so: my apologies; the domain is likely to be down until after the weekend at least.
After the weekend I'll re-target sscce.org (and .com and .net which I acquired a little while back) to a different server that's not suffering from the problem. Or if Andrew prefers I'll target a server under his control. -
Tryin gto back-up my hard drive to a firelite 60 Gb external and the process hangs after only about 30 mb's transferred.
The last line in the terminal log file reads:
lsof: WARNING -- child process 1808 may be hung.
Have tried several times after restart etc-same result
Using Super Duper back-up software. Their support says I should do an archive and install......leery of that.
Any suggestions?
Thank youI did an Archive and re-install-verified both the external Firelite 60gb drive and Mac HD-no problems shown-repaired permissions. Deleted Garage Band per Super Duper Support tech-and it went further into the back-up but hung up again. Each time I receive a different child process # code "hung"-this time it is "child process 384 may be hung 384"
Here is the Terminal Log report:
lsof: WARNING -- child process 384 may be hung.
SDCopy 368 root cwd VDIR 14,2 2958 2 /
SDCopy 368 root txt VREG 14,2 248660 1157312 /SuperDuper!.app/Contents/MacOS/SDCopy
SDCopy 368 root txt VREG 14,2 81316 1234552 /System/Library/CoreServices/CharacterSets/CFUnicodeData-B.mapping
SDCopy 368 root txt VREG 14,2 352454 1234550 /System/Library/CoreServices/CharacterSets/CFCharacterSetBitmaps.bitmap
SDCopy 368 root txt VREG 14,2 17688 1234551 /System/Library/CoreServices/CharacterSets/CFUniCharPropertyDatabase.data
SDCopy 368 root txt VREG 14,2 651264 1534970 /Library/Caches/com.apple.LaunchServices-0140.csstore
SDCopy 368 root txt VREG 14,2 9839648 1524671 /usr/share/icu/icudt32b.dat
SDCopy 368 root txt VREG 14,2 1797576 1531260 /usr/lib/dyld
SDCopy 368 root txt VREG 14,2 4406292 1533481 /usr/lib/libSystem.B.dylib
SDCopy 368 root txt VREG 14,2 512476 1533482 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreText.framework/Versions/A/CoreText
SDCopy 368 root txt VREG 14,2 4607364 1533541 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/CoreGraphics
SDCopy 368 root txt VREG 14,2 1227624 1533483 /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
SDCopy 368 root txt VREG 14,2 1455656 1533586 /usr/lib/libicucore.A.dylib
SDCopy 368 root txt VREG 14,2 801160 1533490 /usr/lib/libobjc.A.dylib
SDCopy 368 root txt VREG 14,2 3435968 1533484 /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonC ore.framework/Versions/A/CarbonCore
SDCopy 368 root txt VREG 14,2 859516 1533486 /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServi ces.framework/Versions/A/OSServices
SDCopy 368 root txt VREG 14,2 3137640 1533534 /System/Library/Frameworks/Security.framework/Versions/A/Security
SDCopy 368 root txt VREG 14,2 1012892 1533512 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ QD.framework/Versions/A/QD
SDCopy 368 root txt VREG 14,2 590292 1533539 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ HIServices.framework/Versions/A/HIServices
SDCopy 368 root txt VREG 14,2 394264 1533535 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ LaunchServices.framework/Versions/A/LaunchServices
SDCopy 368 root txt VREG 14,2 1205064 1533587 /usr/lib/libcrypto.0.9.7.dylib
SDCopy 368 root txt VREG 14,2 1145612 1533681 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libJP2.dylib
SDCopy 368 root txt VREG 14,2 894980 1533491 /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/Desk topServicesPriv
SDCopy 368 root txt VREG 14,2 3755152 1533492 /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
SDCopy 368 root txt VREG 14,2 4707056 1533538 /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.fra mework/Versions/A/HIToolbox
SDCopy 368 root txt VREG 14,2 10859300 1533540 /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
SDCopy 368 root txt VREG 14,2 769892 1533594 /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData
SDCopy 368 root txt VREG 14,2 2226644 1533699 /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore
SDCopy 368 root 0r 0x01e57be0 file struct, ty=0x6, op=0x3823ec
SDCopy 368 root 1w 0x0193eea0 file struct, ty=0x6, op=0x3823ec
SDCopy 368 root 2w 0x01e577f0 file struct, ty=0x6, op=0x3823ec
SDCopy 368 root 3r 0x01e57580 file struct, ty=0x3, op=0x383768
SDCopy 368 root 4r 0x01e57640 file struct, ty=0x3, op=0x383768
SDCopy 368 root 5r 0x01e57a10 file struct, ty=0x3, op=0x383768
SDCopy 368 root 6r VREG 14,2 5425091 1524639 /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.fra mework/Versions/A/Resources/Extras.rsrc
SDCopy 368 root 7r 0x01e576a0 file struct, ty=0x3, op=0x383768
SDCopy 368 root 8u IPv4 0x0239fff4 0t0 TCP 192.168.0.103:49217->c-24-5-135-147.hsd1.ca.comcast.net:http (CLOSE_WAIT)
SDCopy 368 root 9u unix 0x0194c4c0 0t0 ->0x0194cd10
SDCopy 368 root 10u unix 0x0194cd10 0t0 ->0x0194c4c0
SDCopy 368 root 11r 0x01e57450 file struct, ty=0x6, op=0x3823ec
SDCopy 368 root 12w 0x01e57470 file struct, ty=0x6, op=0x3823ec
SDCopy 368 root 13r 0x01e57440 file struct, ty=0x6, op=0x3823ec
SDCopy 368 root 14w 0x01e57460 file struct, ty=0x6, op=0x3823ec
SDCopy 368 root 15r 0x01e57c10 file struct, ty=0x6, op=0x3823ec
SDCopy 368 root 16w 0x01e576f0 file struct, ty=0x6, op=0x3823ec
SDCopy 368 root 17r 0x01e57aa0 file struct, ty=0x6, op=0x3823ec
SDCopy 368 root 18w 0x01e574f0 file struct, ty=0x6, op=0x3823ec
SDCopy 368 root 19r 0x01e57570 file struct, ty=0x3, op=0x383768
SDCopy 368 root 20r 0x01e573f0 file struct, ty=0x3, op=0x383768
SDCopy 368 root 21r VREG 14,2 8170314 289179 /School Folder/Criminology/PDF crim articles/walkersense_and_nonsense_aboutdrugs.pdf
SDCopy 368 root 22r VREG 14,2 8170314 289179 /School Folder/Criminology/PDF crim articles/walkersense_and_nonsense_aboutdrugs.pdf
SDCopy 368 root 23u VREG 14,6 8170314 73 /Volumes/FireLite 60 GB/School Folder/Criminology/PDF crim articles/walkersense_and_nonsense_aboutdrugs.pdf
mike-mangusos-imac-g5:~ amanguso$ sudo lsof | grep SDCopy
lsof: WARNING -- child process 388 may be hung.
lsof: WARNING -- child process 389 may be hung.
SDCopy 368 root cwd VDIR 14,2 2958 2 /
SDCopy 368 root txt VREG 14,2 248660 1157312 /SuperDuper!.app/Contents/MacOS/SDCopy
SDCopy 368 root txt VREG 14,2 81316 1234552 /System/Library/CoreServices/CharacterSets/CFUnicodeData-B.mapping
SDCopy 368 root txt VREG 14,2 352454 1234550 /System/Library/CoreServices/CharacterSets/CFCharacterSetBitmaps.bitmap
SDCopy 368 root txt VREG 14,2 17688 1234551 /System/Library/CoreServices/CharacterSets/CFUniCharPropertyDatabase.data
SDCopy 368 root txt VREG 14,2 651264 1534970 /Library/Caches/com.apple.LaunchServices-0140.csstore
SDCopy 368 root txt VREG 14,2 9839648 1524671 /usr/share/icu/icudt32b.dat
SDCopy 368 root txt VREG 14,2 1797576 1531260 /usr/lib/dyld
SDCopy 368 root txt VREG 14,2 4406292 1533481 /usr/lib/libSystem.B.dylib
SDCopy 368 root txt VREG 14,2 512476 1533482 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreText.framework/Versions/A/CoreText
SDCopy 368 root txt VREG 14,2 4607364 1533541 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/CoreGraphics
SDCopy 368 root txt VREG 14,2 1227624 1533483 /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
SDCopy 368 root txt VREG 14,2 1455656 1533586 /usr/lib/libicucore.A.dylib
SDCopy 368 root txt VREG 14,2 801160 1533490 /usr/lib/libobjc.A.dylib
SDCopy 368 root txt VREG 14,2 3435968 1533484 /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonC ore.framework/Versions/A/CarbonCore
SDCopy 368 root txt VREG 14,2 859516 1533486 /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServi ces.framework/Versions/A/OSServices
SDCopy 368 root txt VREG 14,2 3137640 1533534 /System/Library/Frameworks/Security.framework/Versions/A/Security
SDCopy 368 root txt VREG 14,2 1012892 1533512 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ QD.framework/Versions/A/QD
SDCopy 368 root txt VREG 14,2 590292 1533539 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ HIServices.framework/Versions/A/HIServices
SDCopy 368 root txt VREG 14,2 394264 1533535 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ LaunchServices.framework/Versions/A/LaunchServices
SDCopy 368 root txt VREG 14,2 1205064 1533587 /usr/lib/libcrypto.0.9.7.dylib
SDCopy 368 root txt VREG 14,2 1145612 1533681 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libJP2.dylib
SDCopy 368 root txt VREG 14,2 894980 1533491 /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/Desk topServicesPriv
SDCopy 368 root txt VREG 14,2 3755152 1533492 /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
SDCopy 368 root txt VREG 14,2 4707056 1533538 /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.fra mework/Versions/A/HIToolbox
SDCopy 368 root txt VREG 14,2 10859300 1533540 /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
SDCopy 368 root txt VREG 14,2 769892 1533594 /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData
SDCopy 368 root txt VREG 14,2 2226644 1533699 /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore
SDCopy 368 root 0r 0x01e57be0 file struct, ty=0x6, op=0x3823ec
SDCopy 368 root 1w 0x0193eea0 file struct, ty=0x6, op=0x3823ec
SDCopy 368 root 2w 0x01e577f0 file struct, ty=0x6, op=0x3823ec
SDCopy 368 root 3r 0x01e57580 file struct, ty=0x3, op=0x383768
SDCopy 368 root 4r 0x01e57640 file struct, ty=0x3, op=0x383768
SDCopy 368 root 5r 0x01e57a10 file struct, ty=0x3, op=0x383768
SDCopy 368 root 6r VREG 14,2 5425091 1524639 /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.fra mework/Versions/A/Resources/Extras.rsrc
SDCopy 368 root 7r 0x01e576a0 file struct, ty=0x3, op=0x383768
SDCopy 368 root 8u IPv4 0x0239fff4 0t0 TCP 192.168.0.103:49217->c-24-5-135-147.hsd1.ca.comcast.net:http (CLOSE_WAIT)
SDCopy 368 root 9u unix 0x0194c4c0 0t0 ->0x0194cd10
SDCopy 368 root 10u unix 0x0194cd10 0t0 ->0x0194c4c0
SDCopy 368 root 11r 0x01e57450 file struct, ty=0x6, op=0x3823ec
SDCopy 368 root 12w 0x01e57470 file struct, ty=0x6, op=0x3823ec
SDCopy 368 root 13r 0x01e57440 file struct, ty=0x6, op=0x3823ec
SDCopy 368 root 14w 0x01e57460 file struct, ty=0x6, op=0x3823ec
SDCopy 368 root 15r 0x01e57c10 file struct, ty=0x6, op=0x3823ec
SDCopy 368 root 16w 0x01e576f0 file struct, ty=0x6, op=0x3823ec
SDCopy 368 root 17r 0x01e57aa0 file struct, ty=0x6, op=0x3823ec
SDCopy 368 root 18w 0x01e574f0 file struct, ty=0x6, op=0x3823ec
SDCopy 368 root 19r 0x01e57570 file struct, ty=0x3, op=0x383768
SDCopy 368 root 20r 0x01e573f0 file struct, ty=0x3, op=0x383768
SDCopy 368 root 21r VREG 14,2 8170314 289179 /School Folder/Criminology/PDF crim articles/walkersense_and_nonsense_aboutdrugs.pdf
SDCopy 368 root 22r VREG 14,2 8170314 289179 /School Folder/Criminology/PDF crim articles/walkersense_and_nonsense_aboutdrugs.pdf
SDCopy 368 root 23u VREG 14,6 8170314 73 /Volumes/FireLite 60 GB/School Folder/Criminology/PDF crim articles/walkersense_and_nonsense_aboutdrugs.pdf -
I opened a socket between two machines (Linux-Linux).
The problem is when one of the sides close its socket the socket hangs on the other side (CLOSE_WAIT) till it closes it explicitly.
When I run the same thing on Windows machine the socket close on both machines.
Is there any way to work atound this?
Thanks,
GuyTry running this server and client. What happens?
You really, really, really need to close your sockets.
import java.net.*;
import java.io.*;
public class Accept
public static void main(String[] args)
throws Exception
ServerSocket serverSocket = null;
java.util.LinkedList sockets = new java.util.LinkedList();
try {
serverSocket = new ServerSocket(6666);
} catch (IOException e) {
System.err.println("could not listen on port 6666: " + e);
System.exit(1);
while (true) {
Socket socket;
try {
socket = serverSocket.accept();
} catch (IOException e) {
System.err.println("accept failed: " + e);
Thread.sleep(1000); // Avoid buzz loop
continue;
sockets.add(socket);
System.out.println("accepted " + sockets.size() + " clients");
import java.net.*;
import java.io.*;
public class Connect
public static void main(String args[])
throws Exception
while (true) {
Socket socket = new Socket("localhost", 6666);
socket.close();
} -
WLS 5.1 hangs due to many sockets in CLOSE_WAIT state
Hi,
we are having some serious problems with Weblogic Server 5.1 (SP 6) with
several of our customer installations (Solaris 5.8 and HP UX). The problem
relates to the WLS http server not dealing with socket connections in
CLOSE_WAIT state correctly. We have observered that these can be caused by
Netscape browsers when the end user clicks on the reload button. This causes
the socket connection to be placed in CLOSE_WAIT state, it stays like this
for ever and eventually when there are many sockets in this state WLS runs
out of file descriptors and hangs. We have tried using WLS Apache plugin but
Apache merely passes the CLOSE_WAIT's onto WLS web server. Any help
appreciated on this one,.....
regards Donal.The problem is that your file descriptor table is filling up with sockets in the
CLOSE_WAIT state so there is no more room to put new file descriptors. Any
machine that speaks HTTP is subject to this so you need to apply these changes
both to the web server machine(s) and the application server machine(s).
The way to handle this on Solaris is to decrease the close wait interval:
ndd -set /dev/tcp tcp_close_wait_interval 60000 (Solaris 2.6 and below)
ndd -set /dev/tcp tcp_time_wait_interval 60000 (Solaris 2.7 and above)
(NOTE: It is recommended that you not go below 60 seconds for this, as per
Adrian Cockroft of SUN).
and increase the size of the file descriptor table by adding the following in
/etc/system:
rlim_fd_cur 8192
rlim_fd_max 8192
(NOTE: The close wait interval can also be set in /etc/system, though I don't
remember the name of the parameter off the top of my head.)
Also, make sure that you change the startWebLogic.sh script to grab more file
descriptors with ulimit (or simply remove the ulimit section of the script)...
Hope this helps,
Robert
Donal Mc Ateer wrote:
We have done this. We have made the following 'tweaks' to the Solaris
installation
ndd -set /dev/tcp tcp_keepalive_interval 300000
ndd -set /dev/tcp tcp_ip_abort_interval 2000
ndd -set /dev/tcp tcp_rexmit_interval_max 10000
ndd -set /dev/tcp tcp_fin_wait_2_flush_interval 67500
ndd -set /dev/tcp tcp_time_wait_interval 30000
is there anything else we can do? Is there any way of influencing the WLS
http server handling of these CLOSE_WAIT sockets? Is this being addressed in
WLS 6.0?
-Donal.
"shivu" <[email protected]> wrote in message
news:[email protected]...
try tuning the tcp parameters at solaris level.
(i think tcp_conn_wait)
"Donal Mc Ateer" <[email protected]> wrote:
Hi,
we are having some serious problems with Weblogic Server 5.1 (SP 6) with
several of our customer installations (Solaris 5.8 and HP UX). The
problem
relates to the WLS http server not dealing with socket connections in
CLOSE_WAIT state correctly. We have observered that these can be causedby
Netscape browsers when the end user clicks on the reload button. Thiscauses
the socket connection to be placed in CLOSE_WAIT state, it stays likethis
for ever and eventually when there are many sockets in this state WLSruns
out of file descriptors and hangs. We have tried using WLS Apache pluginbut
Apache merely passes the CLOSE_WAIT's onto WLS web server. Any help
appreciated on this one,.....
regards Donal. -
Hello.My name is Mihai.I have a w120n router.and i have problem with torrents.my client (utorrent) does not upload anything,download works verry well.i have a 24 mb download band.and 2 mb upload.but the upload works only without the router.here i have added a capture of the setting for nat.
http://img535.imageshack.us/img535/5091/router.pngTCP 192.168.0.101:57238 115.84.144.33:29314 TIME_WAIT
TCP 192.168.0.101:57239 84.90.125.175:50375 TIME_WAIT
TCP 192.168.0.101:57240 92.247.237.97:12705 TIME_WAIT
TCP 192.168.0.101:57241 89.134.17.173:32533 TIME_WAIT
TCP 192.168.0.101:57244 89.81.105.4:52594 TIME_WAIT
TCP 192.168.0.101:57245 187.13.155.116:16103 TIME_WAIT
TCP 192.168.0.101:57246 187.20.28.22:52324 TIME_WAIT
TCP 192.168.0.101:57247 217.146.187.123:80 TIME_WAIT
TCP 192.168.0.101:57249 95.76.211.254:47544 TIME_WAIT
TCP 192.168.0.101:57250 188.4.10.125:51405 LAST_ACK
TCP 192.168.0.101:57253 217.146.187.123:80 TIME_WAIT
TCP 192.168.0.101:57260 69.147.97.211:80 ESTABLISHED
TCP 192.168.0.101:57264 86.123.42.40:16126 TIME_WAIT
TCP 192.168.0.101:57268 85.75.74.5:34750 TIME_WAIT
TCP 192.168.0.101:57269 86.211.206.249:42456 TIME_WAIT
TCP 192.168.0.101:57270 89.136.27.32:30614 TIME_WAIT
TCP 192.168.0.101:57271 188.4.171.96:60000 TIME_WAIT
TCP 192.168.0.101:57274 208.74.204.125:80 TIME_WAIT
TCP 192.168.0.101:57275 78.61.37.157:46194 TIME_WAIT
TCP 192.168.0.101:57276 79.119.79.27:19490 TIME_WAIT
TCP 192.168.0.101:57277 86.124.242.72:10400 TIME_WAIT
TCP 192.168.0.101:57278 87.242.20.45:46267 TIME_WAIT
TCP 192.168.0.101:57281 208.74.204.125:80 TIME_WAIT
TCP 192.168.0.101:57285 83.82.254.57:58830 TIME_WAIT
TCP 192.168.0.101:57287 208.74.204.125:80 TIME_WAIT
TCP 192.168.0.101:57288 208.74.204.125:80 TIME_WAIT
TCP 192.168.0.101:57289 208.74.204.125:80 TIME_WAIT
TCP 192.168.0.101:57290 208.74.204.125:80 TIME_WAIT
TCP 192.168.0.101:57294 92.82.118.142:46735 TIME_WAIT
TCP 192.168.0.101:57295 208.74.204.125:80 TIME_WAIT
TCP 192.168.0.101:57296 208.74.204.125:80 TIME_WAIT
TCP 192.168.0.101:57297 208.74.204.125:80 TIME_WAIT
TCP 192.168.0.101:57298 208.74.204.125:80 TIME_WAIT
TCP 192.168.0.101:57299 208.74.204.125:80 TIME_WAIT
TCP 192.168.0.101:57300 208.74.204.125:80 TIME_WAIT
TCP 192.168.0.101:57305 208.74.204.125:80 TIME_WAIT
TCP 192.168.0.101:57306 208.74.204.125:80 TIME_WAIT
TCP 192.168.0.101:57307 188.24.154.108:52052 TIME_WAIT
TCP 192.168.0.101:57309 208.74.204.125:80 TIME_WAIT
TCP 192.168.0.101:57311 208.74.204.125:80 TIME_WAIT
TCP 192.168.0.101:57312 208.74.204.125:80 TIME_WAIT
TCP 192.168.0.101:57313 208.74.204.125:80 TIME_WAIT
TCP 192.168.0.101:57314 208.74.204.125:80 TIME_WAIT
TCP 192.168.0.101:57315 208.74.204.125:80 TIME_WAIT
TCP 192.168.0.101:57317 208.74.204.125:80 TIME_WAIT
TCP 192.168.0.101:57320 89.210.203.234:51057 TIME_WAIT
TCP 192.168.0.101:57324 88.165.168.145:22604 TIME_WAIT
TCP 192.168.0.101:57325 77.85.3.201:16038 TIME_WAIT
TCP 192.168.0.101:57331 188.25.109.250:15835 TIME_WAIT
TCP 192.168.0.101:57333 157.157.217.103:20180 FIN_WAIT_1
TCP 192.168.0.101:57334 78.43.171.118:44846 TIME_WAIT
TCP 192.168.0.101:57336 188.81.59.226:61801 LAST_ACK
TCP 192.168.0.101:57339 109.173.2.145:60933 TIME_WAIT
TCP 192.168.0.101:57344 79.118.87.226:30040 TIME_WAIT
TCP 192.168.0.101:57345 82.76.44.96:47367 TIME_WAIT
TCP 192.168.0.101:57347 89.35.37.10:36471 TIME_WAIT
TCP 192.168.0.101:57352 86.100.134.117:37140 TIME_WAIT
TCP 192.168.0.101:57353 92.249.101.148:24683 TIME_WAIT
TCP 192.168.0.101:57359 188.163.58.220:33285 TIME_WAIT
TCP 192.168.0.101:57364 74.125.39.139:80 ESTABLISHED
TCP 192.168.0.101:57365 74.125.39.139:80 ESTABLISHED
TCP 192.168.0.101:57373 64.77.50.10:80 ESTABLISHED
TCP 192.168.0.101:57376 95.133.136.186:42885 TIME_WAIT
TCP 192.168.0.101:57377 190.160.19.230:23274 TIME_WAIT
TCP 192.168.0.101:57392 194.0.127.108:59103 TIME_WAIT
TCP 192.168.0.101:57394 201.92.159.30:50828 TIME_WAIT
TCP 192.168.0.101:57395 67.215.233.130:80 TIME_WAIT
TCP 192.168.0.101:57398 201.93.217.187:50843 TIME_WAIT
TCP 192.168.0.101:57401 217.136.54.145:46020 TIME_WAIT
TCP 192.168.0.101:57402 93.126.149.80:13312 TIME_WAIT
TCP 192.168.0.101:57403 222.155.17.58:21047 TIME_WAIT
TCP 192.168.0.101:57408 77.67.19.121:80 ESTABLISHED
TCP 192.168.0.101:57410 94.69.153.84:48170 TIME_WAIT
TCP 192.168.0.101:57412 95.169.193.118:21397 TIME_WAIT
TCP 192.168.0.101:57415 198.11.94.127:21838 SYN_SENT
TCP 192.168.0.101:57416 195.80.89.137:19835 SYN_SENT
TCP 192.168.0.101:57417 196.168.94.179:113 SYN_SENT
TCP 192.168.0.101:57418 92.81.249.55:27200 TIME_WAIT
TCP 192.168.0.101:57419 89.38.255.77:31406 TIME_WAIT
TCP 192.168.0.101:57420 198.190.249.16:16054 SYN_SENT
TCP 192.168.0.101:57421 200.54.24.13:30784 SYN_SENT
TCP 192.168.0.101:57422 201.62.166.77:9678 SYN_SENT
TCP 192.168.0.101:57423 84.90.125.175:50375 TIME_WAIT
TCP 192.168.0.101:57424 85.66.190.144:46827 TIME_WAIT
TCP 192.168.0.101:57425 80.130.62.16:54629 SYN_SENT
TCP 192.168.0.101:57426 202.49.248.92:20537 SYN_SENT
TCP 192.168.0.101:57427 203.84.188.4:43872 SYN_SENT
TCP 192.168.0.101:57428 204.188.25.140:37485 SYN_SENT
TCP 192.168.0.101:57431 140.146.109.155:48152 SYN_SENT
TCP 192.168.0.101:57432 205.101.5.220:20934 SYN_SENT
TCP 192.168.0.101:57433 206.39.70.211:17471 SYN_SENT
TCP 192.168.0.101:57434 89.245.13.159:55791 SYN_SENT
TCP 192.168.0.101:57436 84.90.229.190:30733 TIME_WAIT
TCP 192.168.0.101:57437 81.18.65.185:29410 SYN_SENT
TCP 192.168.0.101:57438 187.13.155.116:16103 SYN_SENT
TCP 192.168.0.101:57440 211.68.63.18:25630 SYN_SENT
TCP 192.168.0.101:57441 12.224.156.64:24407 SYN_SENT
TCP 192.168.0.101:57442 208.170.92.83:60106 SYN_SENT
TCP 192.168.0.101:57443 79.116.254.173:33523 SYN_SENT
TCP 192.168.0.101:57444 94.66.201.167:46828 TIME_WAIT
TCP 192.168.0.101:57446 75.152.76.41:47412 SYN_SENT
TCP 192.168.0.101:57447 81.84.60.243:49462 SYN_SENT
TCP 192.168.0.101:57448 81.183.167.166:27845 SYN_SENT
TCP 192.168.0.101:57449 81.95.137.195:50133 SYN_SENT
TCP 192.168.0.101:57451 81.193.246.126:40485 SYN_SENT
TCP 192.168.0.101:57452 81.201.20.16:20692 SYN_SENT
TCP 192.168.0.101:57456 216.188.27.1:8347 SYN_SENT
TCP 192.168.0.101:57459 89.46.136.35:37931 TIME_WAIT
TCP 192.168.0.101:57460 90.227.81.228:41063 TIME_WAIT
TCP 192.168.0.101:57462 85.247.39.253:44569 TIME_WAIT
TCP 192.168.0.101:57463 81.200.22.139:35691 TIME_WAIT
TCP 192.168.0.101:57465 12.243.34.221:42430 SYN_SENT
TCP 192.168.0.101:57466 142.44.141.192:22117 SYN_SENT
TCP 192.168.0.101:58072 72.14.221.100:80 CLOSE_WAIT
TCP 192.168.0.101:58716 72.14.221.100:80 CLOSE_WAIT
TCP 192.168.0.101:59255 72.14.221.101:80 CLOSE_WAIT
TCP 192.168.0.101:59500 72.14.221.101:80 CLOSE_WAIT
TCP 192.168.0.101:59887 72.14.221.100:80 CLOSE_WAIT
TCP 192.168.0.101:60124 72.14.221.101:80 CLOSE_WAIT
TCP 192.168.0.101:60373 72.14.221.101:80 CLOSE_WAIT
TCP 192.168.0.101:60916 72.14.221.101:80 CLOSE_WAIT
TCP 192.168.0.101:61936 72.14.221.100:80 CLOSE_WAIT
TCP 192.168.0.101:62651 72.14.221.101:80 ESTABLISHED
TCP [::]:135 [::]:0 LISTENING
TCP [::]:445 [::]:0 LISTENING
TCP [::]:554 [::]:0 LISTENING
TCP [::]:2869 [::]:0 LISTENING
TCP [::]:3587 [::]:0 LISTENING
TCP [::]:5357 [::]:0 LISTENING
TCP [::]:10243 [::]:0 LISTENING
TCP [::]:23278 [::]:0 LISTENING
TCP [::]:49152 [::]:0 LISTENING
TCP [::]:49153 [::]:0 LISTENING
TCP [::]:49154 [::]:0 LISTENING
TCP [::]:49155 [::]:0 LISTENING
TCP [::]:49156 [::]:0 LISTENING
TCP [::]:49158 [::]:0 LISTENING
TCP [2001:0:4137:9e74:300e:977:b19e:131a]:23278 [2001:0:4137:9e74:2c1b:18c
7:9c47:396a]:62251 TIME_WAIT
TCP [2001:0:4137:9e74:300e:977:b19e:131a]:23278 [2001:0:5ef5:73b8:443:1d98
:b08d:9bfd]:55014 TIME_WAIT
TCP [2001:0:4137:9e74:300e:977:b19e:131a]:23278 [2001:0:5ef5:73ba:4b2:1d74
:a0a8:889]:51220 TIME_WAIT
TCP [2001:0:4137:9e74:300e:977:b19e:131a]:23278 [2001:0:5ef5:73ba:2403:d8c
b:a3ac:b219]:63706 TIME_WAIT
TCP [2001:0:4137:9e74:300e:977:b19e:131a]:23278 [2001:0:5ef5:73ba:285e:2ff
c:a629:cf1b]:54379 TIME_WAIT
TCP [2001:0:4137:9e74:300e:977:b19e:131a]:23278 [2001:0:5ef5:73ba:3c17:200
c:a6d1:2963]:65398 TIME_WAIT
TCP [2001:0:4137:9e74:300e:977:b19e:131a]:23278 [2001:0:5ef5:73ba:3cdf:1a6
d:a677:ed9c]:54484 TIME_WAIT
TCP [2001:0:4137:9e74:300e:977:b19e:131a]:23278 [2001:0:5ef5:73ba:3cdf:1a6
d:a677:ed9c]:54531 TIME_WAIT
TCP [2001:0:4137:9e74:300e:977:b19e:131a]:23278 [2001:0:5ef5:73bc:860:11df
:ab9e:156]:52202 TIME_WAIT
TCP [2001:0:4137:9e74:300e:977:b19e:131a]:23278 [2001:0:5ef5:73bc:283d:203
a:b285:8ead]:61105 TIME_WAIT
TCP [2001:0:4137:9e74:300e:977:b19e:131a]:23278 [2001:0:cf2e:3096:146e:1f2
0:2164:eec5]:56581 SYN_RECEIVED
UDP 0.0.0.0:500 *:*
UDP 0.0.0.0:3544 *:*
UDP 0.0.0.0:3702 *:*
UDP 0.0.0.0:3702 *:*
UDP 0.0.0.0:3702 *:*
UDP 0.0.0.0:3702 *:*
UDP 0.0.0.0:4500 *:*
UDP 0.0.0.0:5004 *:*
UDP 0.0.0.0:5005 *:*
UDP 0.0.0.0:5355 *:*
UDP 0.0.0.0:6771 *:*
UDP 0.0.0.0:23278 *:*
UDP 0.0.0.0:49486 *:*
UDP 0.0.0.0:51646 *:*
UDP 0.0.0.0:51648 *:*
UDP 0.0.0.0:53525 *:*
UDP 0.0.0.0:53701 *:*
UDP 0.0.0.0:55044 *:*
UDP 0.0.0.0:60477 *:*
UDP 0.0.0.0:63604 *:*
UDP 0.0.0.0:64068 *:*
UDP 0.0.0.0:64156 *:*
UDP 127.0.0.1:1900 *:*
UDP 127.0.0.1:49865 *:*
UDP 127.0.0.1:53072 *:*
UDP 127.0.0.1:53073 *:*
UDP 127.0.0.1:59087 *:*
UDP 192.168.0.101:137 *:*
UDP 192.168.0.101:138 *:*
UDP 192.168.0.101:1900 *:*
UDP 192.168.0.101:1900 *:*
UDP 192.168.0.101:5353 *:*
UDP 192.168.0.101:49264 *:*
UDP 192.168.0.101:49270 *:*
UDP 192.168.0.101:50279 *:*
UDP 192.168.0.101:50703 *:*
UDP 192.168.0.101:51073 *:*
UDP 192.168.0.101:51466 *:*
UDP 192.168.0.101:51515 *:*
UDP 192.168.0.101:51557 *:*
UDP 192.168.0.101:51668 *:*
UDP 192.168.0.101:51946 *:*
UDP 192.168.0.101:52236 *:*
UDP 192.168.0.101:52762 *:*
UDP 192.168.0.101:52775 *:*
UDP 192.168.0.101:53064 *:*
UDP 192.168.0.101:53114 *:*
UDP 192.168.0.101:53310 *:*
UDP 192.168.0.101:53378 *:*
UDP 192.168.0.101:53440 *:*
UDP 192.168.0.101:53587 *:*
UDP 192.168.0.101:53858 *:*
UDP 192.168.0.101:54137 *:*
UDP 192.168.0.101:54164 *:*
UDP 192.168.0.101:54456 *:*
UDP 192.168.0.101:54465 *:*
UDP 192.168.0.101:55228 *:*
UDP 192.168.0.101:55235 *:*
UDP 192.168.0.101:55382 *:*
UDP 192.168.0.101:55461 *:*
UDP 192.168.0.101:55462 *:*
UDP 192.168.0.101:55507 *:*
UDP 192.168.0.101:55557 *:*
UDP 192.168.0.101:55591 *:*
UDP 192.168.0.101:55635 *:*
UDP 192.168.0.101:56008 *:*
UDP 192.168.0.101:56260 *:*
UDP 192.168.0.101:56467 *:*
UDP 192.168.0.101:56591 *:*
UDP 192.168.0.101:56650 *:*
UDP 192.168.0.101:56656 *:*
UDP 192.168.0.101:56860 *:*
UDP 192.168.0.101:56968 *:*
UDP 192.168.0.101:57043 *:*
UDP 192.168.0.101:57067 *:*
UDP 192.168.0.101:57285 *:*
UDP 192.168.0.101:57570 *:*
UDP 192.168.0.101:57652 *:*
UDP 192.168.0.101:57830 *:*
UDP 192.168.0.101:57927 *:*
UDP 192.168.0.101:58396 *:*
UDP 192.168.0.101:58839 *:*
UDP 192.168.0.101:59086 *:*
UDP 192.168.0.101:59221 *:*
UDP 192.168.0.101:59286 *:*
UDP 192.168.0.101:59492 *:*
UDP 192.168.0.101:59764 *:*
UDP 192.168.0.101:59808 *:*
UDP 192.168.0.101:59995 *:*
UDP 192.168.0.101:60094 *:*
UDP 192.168.0.101:60247 *:*
UDP 192.168.0.101:60400 *:*
UDP 192.168.0.101:60758 *:*
UDP 192.168.0.101:61117 *:*
UDP 192.168.0.101:61278 *:*
UDP 192.168.0.101:61588 *:*
UDP 192.168.0.101:62025 *:*
UDP 192.168.0.101:62130 *:*
UDP 192.168.0.101:62403 *:*
UDP 192.168.0.101:62603 *:*
UDP 192.168.0.101:62963 *:*
UDP 192.168.0.101:63030 *:*
UDP 192.168.0.101:63111 *:*
UDP 192.168.0.101:63157 *:*
UDP 192.168.0.101:63158 *:*
UDP 192.168.0.101:63434 *:*
UDP 192.168.0.101:63477 *:*
UDP 192.168.0.101:63615 *:*
UDP 192.168.0.101:63858 *:*
UDP 192.168.0.101:64170 *:*
UDP 192.168.0.101:64246 *:*
UDP 192.168.0.101:64351 *:*
UDP 192.168.0.101:64366 *:*
UDP 192.168.0.101:64496 *:*
UDP 192.168.0.101:64518 *:*
UDP 192.168.0.101:64621 *:*
UDP 192.168.0.101:64671 *:*
UDP 192.168.0.101:64805 *:*
UDP 192.168.0.101:64830 *:*
UDP 192.168.0.101:65445 *:*
UDP [::]:500 *:*
UDP [::]:3540 *:*
UDP [::]:3702 *:*
UDP [::]:3702 *:*
UDP [::]:3702 *:*
UDP [::]:3702 *:*
UDP [::]:4500 *:*
UDP [::]:5004 *:*
UDP [::]:5005 *:*
UDP [::]:5355 *:*
UDP [::]:23278 *:*
UDP [::]:51647 *:*
UDP [::]:51649 *:*
UDP [::]:55045 *:*
UDP [::]:64157 *:*
UDP [::1]:1900 *:*
UDP [::1]:59085 *:*
UDP [fe80::e19a:e73f:f5cb:8b8a%12]:1900 *:*
UDP [fe80::e19a:e73f:f5cb:8b8a%12]:59084 *:*
C:\Users\synco>
i did not find how to attach a file,this is the best i found.
Message Edited by synco on 03-09-2010 10:54 AM -
Re: WLS 6.0 SP2 hangs due to many sockets in CLOSE_WAIT state
We have the same issue with HPUX and Weblogic 5.1 SP8. In fact, we get
errors on the ListenThread because occasionally it (the ListenThread)
says too many files open. Running a monitoring tool - the process
typically only has ~130 file handles open at any time. When we start
getting a lot of sockets "stuck" in close_wait state the number of open
files increases dramatically occasionally freezing the server until (I
believe) the OS steps in and cleans house.
For those curious, our box is configured to have a max of 1024 files
open. Please don't even suggest that we raise that parameter because it
is already high enough.
We are tempted to use apache as the webserver and proxy request through
apache to weblogic. Apache doesn't suffer from this issue AFAIK.
-Tim
sogal nagavardhan wrote:
Hi !!
We are using weblogic 6.0 SP2 with jdk1.3.1 running on windows 2000 platform.
Currently we are using running some stablity tests and noticing that there are
lot of sockets in close_wait state and handle count keeps going up and eventually
crashes the weblogic. We also tried reducing the TcpTimedWaitDelay as suggested
in this newsgroup, and we are still noticing this problem. Does any body have
the same issue?. is this a know problem with weblogic http server?. and finally
any fixes or workarounds to this issue.
Thanks
Sogal.NBEA acknowledges this problem in 6.0 SP2 with iPlanet plug-in.
Solution that they recommend is to use 6.1 SP2 plug-in (they claim
full compatibility). Also, you may have to set KeepAliveEnabled to
false in obj.conf (the problem is in wrong pooling).
Hope it helps,
Bala
Robert Patrick <[email protected]> wrote in message news:<[email protected]>...
There are a couple of issues.
1.) You need to tune the machine running the web server and the machine
running WebLogic to make sure that it is configured appropriately for a
high-volume HTTP server. See
http://e-docs.bea.com/wls/platforms/sun/index.html for details on tuning
Solaris.
2.) I believe that there is a bug in the plugins in 6.0 where it is not
properly closing sockets. Try using the plugin from WLS 6.1 SP2...
Hope this helps,
Robert
Kevin Phillips wrote:
Tim Funk <[email protected]> wrote:
I am experiencing similar problems with WL 6.0 SP2 on Solaris 2.6.
We are already proxying all HTTP traffic through a
cluster of apache servers. Unfortuantely, the apache-WL
bridge seems to work so efficiently that our servers are
still flooded with open sockets in the TCP_CLOSE_WAIT state.
It seems to be bound by WebLogic's capacity to respond to
the requests in a speedy enough fashion.
Anybody have any suggestions?
Kevin
We have the same issue with HPUX and Weblogic 5.1 SP8. In fact, we get
errors on the ListenThread because occasionally it (the ListenThread)
says too many files open. Running a monitoring tool - the process
typically only has ~130 file handles open at any time. When we start
getting a lot of sockets "stuck" in close_wait state the number of open
files increases dramatically occasionally freezing the server until (I
believe) the OS steps in and cleans house.
For those curious, our box is configured to have a max of 1024 files
open. Please don't even suggest that we raise that parameter because
it
is already high enough.
We are tempted to use apache as the webserver and proxy request through
apache to weblogic. Apache doesn't suffer from this issue AFAIK.
-Tim
sogal nagavardhan wrote:
Hi !!
We are using weblogic 6.0 SP2 with jdk1.3.1 running on windows 2000
platform.
Currently we are using running some stablity tests and noticing that
there are
lot of sockets in close_wait state and handle count keeps going up
and eventually
crashes the weblogic. We also tried reducing the TcpTimedWaitDelay
as suggested
in this newsgroup, and we are still noticing this problem. Does any
body have
the same issue?. is this a know problem with weblogic http server?.
and finally
any fixes or workarounds to this issue.
Thanks
Sogal.N -
Hello,
I am getting accumulative CLOSE_WAIT connections on the weblogic side. The number
of CLOSE_WAIT connections keep growing and growing and each connection appears
to use up one thread on weblogic.
It all ends up with weblogic server toasted becuase it runs out of threads.
My platform is weblogic 6.1SP4 on Solaris and the webserver is on another Solaris
machine.
My question is: ¿Is this an applications issue (code)? ¿Is it a weblogic issue?
TIA
CristinaHi there,
Yes, we do have the same problem but we have the WL 81 SP2 installed on Solaris box.
For us this happens whenever we restart the managed server instances using the node manager.
I suppose the Node Manager configuration is Error free.
Thanks,
Karthi.
Maybe you are looking for
-
Hi there, I just bought a web premium CS 4 suite. I am able to use all the other programmes however I am unable to use the photoshop CS 4. On start up, while it loads "reading preferences", another pop-up window appears with the message "Adobe Photos
-
Firstly, apologies of this has been covered before ... I've had a look around and haven't been able to find anything similar. Since installing 10.5, I'm finding that, periodically, when I open System Preferences and go to 'Desktop & Screensavers', th
-
This is crap!!!!! Why do NONE of my apps work since the cloud?
Mac OSX 10.7.5, and NONE of the Adobe apps work right now that the cloud is in place. I cannot even get photoshop 3 or 6 or CC to open! Spinning ball, and nothing. HELP!!!!!!!
-
ORA-19502 while adding a tablespace
Hello All, I am using ORACLE 10g R2, on LINUX, red hat 5 When i am trying to add a tablespace through Enterprise manager I am getting the below error: Failed to commit: ORA-19502: write error on file "/u01/app/oracle/oradata/IMALREF/MDB_O10_DATA", bl
-
How can i change de name of my icloud account?
Here's the problem. I've been using the same itunes account for years. It's on my girlfriends name. Since I've been using my macbook pro for my company, everythime I send an ical invitation to someone they see her name instead of my name. So my que