fault tolerance client /server

[mark smith]

hi

i use a very basic client/server socket program

very similar to sun:
http://java.sun.com/docs/books/tutorial/networking/sockets/clientServer.html

many client can connect to the server...

i would like to add a fault tolerance...

a client try to connect a few time... that don't work, the client try to the second server...

does a need to do something similar to

public class KKMultiServer {
    public static void main(String[] args) throws IOException {
        ServerSocket serverSocket1 = null;
        ServerSocket serverSocket1 = null;
        boolean listening = true;
 
        try {
            serverSocket = new ServerSocket(4444);
            serverSocket = new ServerSocket(4445);
        } catch (IOException e) {
            System.err.println("Could not listen on port.");
            System.exit(-1);
        }
 
        while (listening){
    new KKMultiServerThread(serverSocket1.accept()).start();
            new KKMultiServerThread(serverSocket2.accept()).start();
         }
        serverSocket1.close();
        serverSocket2.close();
    }
}

thanks

[Stan James]

Something like that. Here's a very similar method that starts up servers for me. Configuration has a list of ports separated by commas, eg 9000,9002,9004

private void startServers()
{
    String[] ports = HTTP_PORT.split( "," );
    servers = new HTTPServer[ports.length];
    for (int i = 0; i < ports.length; i++)
    {
        servers[i] = new HTTPServer( Integer.parseInt( ports[i] ) );
        new Thread( servers[i] ).start();
    }
}

This thread runs out and terminates shortly after this startup. The server threads run until told to stop and then close their own resources.

Does that kind of affirm your direction?
[ October 01, 2005: Message edited by: Stan James ]

[mark smith]

ya

and client level what you do?

[Stan James]

Nothing - the client is a browser. In another application we had code in a Swing client to fail over from one server to another after "n" tries. It could also fail back later ... exactly the same code again, just worked its way down an array of port numbers and then started over I think.

[mark smith]

ok but my client is not in a browser... for me the port change...