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 <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]> > 17/03/2006 18:10 > > Please respond to > "Apache AXIS C Developers List" <[email protected]> > > To > > "Apache AXIS C Developers List" <[email protected]> > > 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. >
