Re: CLOSE_WAIT issues

Aurelien Minet <[email protected]> Tue, 25 Jul 2006 21:26:29 +0200
Newsgroups gmane.comp.web.webobjects.admin
Message-ID <[email protected]>
Sacha Michel Mallais wrote:
> On Jul 25, 2006, at 11:40 AM, John Pollard wrote:
>
>> I have confirmed WO5.2.4 from /Library/Receipts
>> It is the Developer version though, with a deployment license added,
>> I wonder if that could be a problem. We deploy on Mac OS X Client
>> boxes, as there doesn't seem much point in splashing out for Mac OS X
>> Server. Could this be our undoing on this issue?
>
> I suppose it is possible that there is some difference between the 2
> versions, but I don't think so.  I don't recommend what you're doing
> (simply because spending even a few hours configuring a client box is
> usually not worth it if you can buy something that will work
> out-of-the-box), but I would expect to see missing classes or
> something along those lines if that was your problem.
>
> Have you verified that the CLOSE_WAIT does, in fact, occur when
> communicating to your DB?  Or is it between wotaskd and the apps.  My
> experience is with the latter...
>
>
> sacha
>
>
> --Sacha Michel Mallais             400 kg chimp
> Global Village Consulting Inc.   http://www.global-village.net/
> PGP Key ID: 7D757B65             AIM: smallais
> "Choke on that, causality!"  -- the Professor, "Futurama"
>
>
> _______________________________________________
> WebObjects-admin mailing list
> [email protected]
> http://www.omnigroup.com/mailman/listinfo/webobjects-admin

Hi all,

I have CLOSE_WAIT , mostly with DB connections, but I have transactions
in JavaMonitor with no active session.
A TCP connection in CLOSE_WAIT means that the remote close the
connection (FIN) and the local system has yet say ok (ACK). This state
should ends when the application tries to use the file descriptor, if it
is a DB connection (which have timeout) it would try to reconnect to it,
a client it ends the session .....
You may check the version of your jdcb driver, and check if it has no
problem with IPV6 ( your lsof report TCP connection in IPV6 on the loopback.
Putting your application un debug mode may help.

Aurelien


-- 
Aurelien Minet
Direction des Systemes d'Information
Universite Rene Descartes