Production Instance : CLOSE_WAIT Connection Issue

Question

Here is part of my code:

if(s.equals("Fluff")){
             Desktop c=Desktop.getDesktop();
             c.browse(new URI("https://www.youtube.com/watch?v=_9kdZ07BCFQ"));
         }

I'd like for the user to be able to type 'stop' to kill the web page. I have looked online, but all I am seeing is window.close(). I tried it, but it didn't work - I think because I am using Desktop instead of window. How would I go about doing this?

I'm new to coding, so the solution may be obvious, I just don't see it. Explain thoroughly - I'd like to learn, not copy/paste.

Solution

Some clients don't properly close the TCP connection when they're done. That's out of your control. These generally time out after a bit, and don't create too much of a problem, other than cluttering the listing you get from netstat -an and similar.

So, why you are having a problem with it?

This might be pertinent: What limits the maximum number of connections on a Linux server?

Comments

[mannysz]

Same problem here! But the strange thing is I am running workers that are connected to my local nginx using unix socket. And these workers are stuck with a connection on load balancer on SSL port. I tried many other solutions and it keeps happening (changed nginx to apache, and uwsgi to gunicorn for python workers). I believe its a ELB problem. And the worst thing is that sometimes it goes crazy an floods my EC2 instances with CLOSE_WAIT connections (more than 100k connections). Amazon support says its not an ELB issue. Any hints?

[poige]

Earlier, all of the clients on the Internet were connecting over rather unreliable and slow networks and TCP states weren't gone crazy. )

[mc0e]

Does this actually work? My understanding is that those CLOSE_WAIT states are being maintained by the OS, and restarting apache processes should have no effect.