SocketException

Article View: borland.public.jbuilder.java.language

Article #727

Back to borland.public.jbuilder.java.language Previous Next

#727

From: lredmond
Date: Fri, 10 Dec 2004 01:23

2 lines
1378 bytes

I have an application that has a dedicated connection to a server.  I send/receive messages via the connection.  Whenever they reboot the server it causes all messages sent by my client app to throw a socket exception when reading the replies from sending the messages. I must restart the client app for it to start functioning agian.  I have added code and even ran it through the debugger to check the connection state, the closed state of the socket and connecte = true and closed = false.  is there soemthing I can check on the socket to prevent having to restart the client?

Technical Details

Message-ID: <41b8fa86$1@newsgroups.borland.com>

Path:

arc1-ca.pugleaf.net!g2news1.google.com!news2.google.com!proxad.net!proxad.net!194.117.148.138.MISMATCH!pe2.news.blueyonder.co.uk!blueyonder!news-peer-test!btnet!newsfeed.bt.es!caladan.landsraad.net!newsgroups.borland.com!not-for-mail

Show Full Headers

Complete Article Headers

X-Google-Thread: f74b3,f3a9b798501ee744,start
X-Google-Attributes: gidf74b3,public
X-Google-Language: ENGLISH,ASCII-7-bit
From: "lredmond" <sirlanslot@aol.com>
Sender: "lredmond" <sirlanslot@aol.com>
Reply-To: "lredmond" <sirlanslot@aol.com>
Subject: SocketException
Newsgroups: borland.public.jbuilder.java.language
X-User-Info: 24.110.97.165     
NNTP-Posting-Host: 207.105.83.66
Message-ID: <41b8fa86$1@newsgroups.borland.com>
Date: 9 Dec 2004 17:23:18 -0800
X-Trace: newsgroups.borland.com 1102641798 207.105.83.66 (9 Dec 2004 17:23:18 -0800)
Lines: 2
Path: arc1-ca.pugleaf.net!g2news1.google.com!news2.google.com!proxad.net!proxad.net!194.117.148.138.MISMATCH!pe2.news.blueyonder.co.uk!blueyonder!news-peer-test!btnet!newsfeed.bt.es!caladan.landsraad.net!newsgroups.borland.com!not-for-mail