Page History

...

1. SocketBindException saying that the HA Port is already bound

   This exception indicates that some other program that is running on the HA port or the last instance of the server is not properly killed.
   Stop/kill the application which is holding up the port and start the server again or choose a different HA port. But changing this means that there needs to be a change in the Backup Servers' configuration for its Backup Server port. 

2. None of the servers starting up

   Both the servers are in WAITING state and the Primary Server is trying to connect to its Backup Server.
   
   This exception indicates that the Backup Server IP and port numbers are wrong for both the server configurations.
   
   Example: Server console when it cannot connect to the Backup Server.
    
   
   The figure below illustrates a situation where the server is not able to connect to the Backup Server. If it is already connected, then there is a problem with the configuration. The message prints the IP address and the port to which it is trying to connect to establish the HA channel.
   Check if the Backup Server is running in the printed IP address and port.
   
   
   Figure 1: Server unable to connect to the Backup Server 

3. One of the HA Servers switched into Active or Passive Sync and it hangs there, but the other seems to be in WAITING state for a long time trying to connect to the Backup Server.

   This exception indicates that your configuration for the Backup Servers does not match at the end where the server is still in WAITING state, but the Backup Server is still able to connect. This will cause the Backup Server to hand indefinitely as it expects a Synchronization Complete Notification which is never going to be delivered.
   
   
   Figure 2: The server hanging in one of the synchronization states 

4. Both servers go to Standalone/Active state in replicated/shared mode respectively if the network link between them is broken.

   This can happen if the servers do not refer to the same LockFile. 

5. The server in replicated mode shuts down on boot up

   This can happen if the LockFile specified is not valid or the machine hosting the LockFile is not allowing the server to acquire a lock. Figure 3 illustrates the server shutting down on boot up.
   
   
   Figure 3: The server shutting down on boot up

Handling "Client ID Already Exists" exception

This error can occur when FES is force closed when the break points are in place or when break point addition fails due to any other reason on previous attempt. In such a case the client corresponding to the previous connection needs to be removed. Follow the steps below and add the break point again.

Anchor
IDConnect IDConnect

Identifying the Connection 

1. Login to ESB Dashboard. Under the Server Status node, select the Enterprise Server and then Select Connections. 
    

2. Check for PTP connections related to unclosed break points. The connection names will have the pattern <CLIENT_ID>,<Number> .

   Tip
   Client IDs will be of the format ESBX_SYSTEM<Event Process Name><Version><RouteName>C and ESBXSYSTEM<EventProcessName><Version><COMPONENT_NAME>_<RouteName>

3. Copy the ClientIDs from here.
   
   Image Added

Closing Identified Connections

1. Log into FES-JMX and navigate to Admin Service node as shown below
   Image Added
   
   
2. Right-click on the node and click – ViewOperations which opens the dialog as shown below
    
   Image Added
   
   
3. Choose the operation disconnectClient(clientID) and provide the clientIDs from the above section.
    
4. Click on the disconnectClient button, a value true will be seen in the Result Tab and the client will get disconnected. 

You can verify this by refreshing the dashboard list of connections found above section.