>Okay so this means, you would prefer my proposed solution #1? >That was my inclination too. Proposed solution #1 without the errno check. My idea : get the service code in a loop for (i = 0; i < RETRIES; i++) { if (send_request() < 0) continue; if (read_reply() == 0) break; } --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
- FW: problem w/ ajp13 - if Tomcat is shutdown Shinta Tjio
- Re: FW: problem w/ ajp13 - if Tomcat is shutdown Dan Milstein
- RE: FW: problem w/ ajp13 - if Tomcat is shutdown Shinta Tjio
- RE: FW: problem w/ ajp13 - if Tomcat is shutdown oliver2, andy
- RE: FW: problem w/ ajp13 - if Tomcat is shutdown Shinta Tjio
- RE: FW: problem w/ ajp13 - if Tomcat is shutdown oliver2, andy
- RE: FW: problem w/ ajp13 - if Tomcat is shutdown Shinta Tjio
- RE: FW: problem w/ ajp13 - if Tomcat is shutdown GOMEZ Henri
- RE: FW: problem w/ ajp13 - if Tomcat is shutdown Shinta Tjio
- Re: FW: problem w/ ajp13 - if Tomcat is shutdown GOMEZ Henri
- Re: FW: problem w/ ajp13 - if Tomcat is shutdown Dan Milstein
- RE: FW: problem w/ ajp13 - if Tomcat is shutdown Shinta Tjio
- RE: FW: problem w/ ajp13 - if Tomcat is shutdown GOMEZ Henri
- RE: FW: problem w/ ajp13 - if Tomcat is shutdown GOMEZ Henri
- Re: FW: problem w/ ajp13 - if Tomcat is shutdown Dan Milstein
- RE: FW: problem w/ ajp13 - if Tomcat is shutdown Shinta Tjio
- RE: FW: problem w/ ajp13 - if Tomcat is shutdown GOMEZ Henri
- Re: FW: problem w/ ajp13 - if Tomcat is shutdown Dan Milstein
- Re: FW: problem w/ ajp13 - if Tomcat is shutdown Dan Milstein
- RE: FW: problem w/ ajp13 - if Tomcat is shutdown Shinta Tjio