Path: csiph.com!usenet.pasdenom.info!gegeweb.org!eternal-september.org!feeder.eternal-september.org!mx04.eternal-september.org!.POSTED!not-for-mail From: Knute Johnson Newsgroups: comp.lang.java.programmer Subject: Re: Strange Socket problem Date: Mon, 05 Mar 2012 09:44:22 -0800 Organization: A noiseless patient Spider Lines: 21 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Injection-Date: Mon, 5 Mar 2012 17:44:23 +0000 (UTC) Injection-Info: mx04.eternal-september.org; posting-host="mz/LDSJwiWnk3Jnnqg7x+Q"; logging-data="24684"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18Bui9YdUEtmWM5rBr0wIWd" User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 In-Reply-To: Cancel-Lock: sha1:qicWEy96oU2YNyK/pYu/UMiaSwI= Xref: csiph.com comp.lang.java.programmer:12716 On 3/4/2012 9:00 PM, John B. Matthews wrote: >> Because the only thing two things I can think of right now are bad >> data causing an exception that I'm not seeing for some reason or >> something in the TCP/IP connection sequence that is blocking the >> socket creation and hanging the code at that point. > > Any chance they started preemptively rebooting errant hardware at a time > that correlates with your observation? I think that is likely but I have no way to get that information. The company holds tight to information like that. I've put in code to trap any Throwable and also to look for the possibility of bad data. Now I just have to wait and see if it happens again. Thanks for looking. -- Knute Johnson