Initializing the LE When existing leader is down about epzilla HOT 5 CLOSED

The main barrier behind this now solved. Now every node/dispatcher can identify 
and can 
update the node list/dispatcher list before the leader election starts up 
again. So the 
LE side of this request now fixed. Have to complete the node/dispatcher side 
work now.

What do you mean by "node/dispatcher side" work, re-initializing the STM with 
the new 
Leader as the server and connecting the others as clients?

Yes. That part. Since you have pointed out the place to start work, I have done 
some 
thing like following.

I have moved the Leader Identification part which was in the leaderReg.Main to 
a new 
method. 
 public static void startSTM(){
                String leader = "";
                while (leader.equalsIgnoreCase("")) {
                    leader = LeaderElectionInitiator.getLeader();
                }
                if (leader.equalsIgnoreCase(ipAddress)) {
                    NodeController.setLeader(true);
                    initSTM();
                } else {
                    NodeController.setLeader(false);
                    NodeController.setLeaderIP(leader);
                    initSTM();
                }

    }

and in the NodeAsNonLeader, I have done the following. The section below the 
comment 
//Initializing LE. 

public static void checkServerStatus() {
        final java.util.Timer timer1 = new java.util.Timer();
        timer1.schedule(new TimerTask() {
            @Override
            public void run() {
                final SocketClient.Status serverStatus=client.getStatus();
                if (serverStatus == SocketClient.Status.DISCONNECTED) {
                    NodeUIController.appendTextToStatus("Server Status :" + 
serverStatus);
                    this.cancel();
                    //Initializing LE
                    org.epzilla.clusterNode.leaderReg.Main.triggerLEFromRemote();                    
org.epzilla.clusterNode.leaderReg.Main.startSTM();
                }
            }
        }, 10, 1000);
    }

Now this works fine and elects a leader and starts a new UI and STM. But there 
are 2 
issue AKAIK. 

1. The previous UI is not hidden. So now there are 2 UIs :).
2. The content of the previous STM is not included in the new STM.

So as our STM expert, dishan has to work on 2 and as our UI expert Chathura has 
to 
work on 1. 

I'm attaching the current work as attachments.

I have not committed the current work to the repo since i wasn't sure it was 
the 
correct way of doing that.

I have tested the fix provided by Dishan on #r814 and verified the correctness. 
I am changing the status to Verified.