Return-Path: Delivered-To: apmail-ws-axis-c-dev-archive@www.apache.org Received: (qmail 46806 invoked from network); 17 Mar 2006 19:34:47 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 17 Mar 2006 19:34:47 -0000 Received: (qmail 17605 invoked by uid 500); 17 Mar 2006 19:34:46 -0000 Delivered-To: apmail-ws-axis-c-dev-archive@ws.apache.org Received: (qmail 17580 invoked by uid 500); 17 Mar 2006 19:34:46 -0000 Mailing-List: contact axis-c-dev-help@ws.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: "Apache AXIS C Developers List" Reply-To: "Apache AXIS C Developers List" Delivered-To: mailing list axis-c-dev@ws.apache.org Received: (qmail 17418 invoked by uid 99); 17 Mar 2006 19:34:45 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 17 Mar 2006 11:34:45 -0800 X-ASF-Spam-Status: No, hits=0.5 required=10.0 tests=DNS_FROM_RFC_ABUSE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of amra@us.ibm.com designates 32.97.182.142 as permitted sender) Received: from [32.97.182.142] (HELO e2.ny.us.ibm.com) (32.97.182.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 17 Mar 2006 11:34:44 -0800 Received: from d01relay02.pok.ibm.com (d01relay02.pok.ibm.com [9.56.227.234]) by e2.ny.us.ibm.com (8.12.11/8.12.11) with ESMTP id k2HJYKTL007822 for ; Fri, 17 Mar 2006 14:34:20 -0500 Received: from d01av03.pok.ibm.com (d01av03.pok.ibm.com [9.56.224.217]) by d01relay02.pok.ibm.com (8.12.10/NCO/VER6.8) with ESMTP id k2HJYKR5145938 for ; Fri, 17 Mar 2006 14:34:20 -0500 Received: from d01av03.pok.ibm.com (loopback [127.0.0.1]) by d01av03.pok.ibm.com (8.12.11/8.13.3) with ESMTP id k2HJYKJJ001720 for ; Fri, 17 Mar 2006 14:34:20 -0500 Received: from d27ml101.rchland.ibm.com (d27ml101.rchland.ibm.com [9.10.229.40]) by d01av03.pok.ibm.com (8.12.11/8.12.11) with ESMTP id k2HJYKCB001710 for ; Fri, 17 Mar 2006 14:34:20 -0500 In-Reply-To: To: "Apache AXIS C Developers List" Subject: Re: monitor changes causing hang? MIME-Version: 1.0 X-Mailer: Lotus Notes Release 7.0 HF85 November 04, 2005 Message-ID: From: Nadir Amra Date: Fri, 17 Mar 2006 13:34:06 -0600 X-MIMETrack: Serialize by Router on d27ml101/27/M/IBM(Release 7.0|August 18, 2005) at 03/17/2006 01:34:19 PM, Serialize complete at 03/17/2006 01:34:19 PM Content-Type: text/plain; charset="US-ASCII" X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N OK, I do not think that solves any problems you may have been encountering so I may comment it out (if you think otherwise, we can always make it dependent on platform. I also think that for client sockets that "socket.setKeepAlive(false);" should be "socket.setKeepAlive(true);". This will ensure that the monitor will not hang if for example the server was to be rebooted - i.e. errors on connections will be sent to client app as soon as possible instead of waiting indefinately. Let me know if doing this is a problem. Nadir K. Amra John Hawkins wrote on 03/17/2006 12:36:08 PM: > > Reason: desperation ! I tried sooo many combinations I just put them > all on at once at one point and when it worked I ran ! > > > > > > Nadir Amra > 17/03/2006 18:10 > > Please respond to > "Apache AXIS C Developers List" > > To > > "Apache AXIS C Developers List" > > cc > > Subject > > Re: monitor changes causing hang? > > > > > John, > > Is there any reason to do "socket.setReuseAddress(true);" on client > sockets? The client sockets do not explicity bind to any address so I do > not think that setReuseAddress() is appropriate, and I am not even sure > what the ramifications are in invoking this method. I am going to test > commenting this out but was wondering if there was a reason behind the > call. >