Hello Aurelien, Yep, we upgraded to 5.2.1 - 5.2.2 - 5.2.3 - 5.2.4.
We do sometimes see broken pipe exception in our logs, I heard that this generally happens when the connection between woadptor and browser is idle for certain amount of time, whcih generally means the connection between woadaptor and browser is broken. Am I right? How can we find dead locks in our application? Please advise a solution as to how to determine which part of the application is causing this problem. Thanks for your reply. Thank You Shravan ---------------------------- On Tue, April 22, 2008 9:11 pm, Aurélien Minet wrote: > Hi, > >> We have been battered by CLOSE_WAIT processes and instances hang. >> >> We are running our application on Solaris 5.8 boxes with WebObjects >> 5.2.4, Java 1.4.2_17. > The 5.2 updates are "cumulative", do you apply 5.2.3 update ? (and 5.2.1 > 5.2.2) > it fix a bug about close_wait ( > http://docs.info.apple.com/article.html?artnum=107873 ) >> >> We have collected some process dumps and consulted Sun, they analyzed >> and blame our code, alas!!! >> >> We see CLOSE_WAIT state of a process for both java and httpd processes. > Is the java process is your app or the wotaskd ? > If it is your app, is it the only application that has the problem ? >> We see degradation in our application performance as the day >> progresses and our app becomes unresponsive various times, we restart >> the app various times during day. > Don't you have java exception: broken pipe in your application logs ? >> >> Could any one please advise us a solution to find the reason for >> instance hang or fix CLOSE_WAIT processes generation. > You may also look for deadlocks in your apps. > > Regards > > Aurelien > > -- Thank You Shravan Kumar. M effigent India Pvt Ltd., _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-deploy mailing list (Webobjects-deploy@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-deploy/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
