🚀 go-pugleaf

lredmond wrote:

> 
> 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?

Are you using a constantly connected state for the Client Sockets to server
connectivity? IF so, I would suggest you didn't.

Also what about threading the socket connections? Perhaps creating  a reboot
message to send to all clients, before restarting the server.

If the socket is not required to maintain state, you may want to look at
replacing the current socket to socket communication with JMS.