Server manager failover limitations

The failover abilities of server managers are limited. When a server manager becomes unavailable in a hard way such as a network interruption or a machine crash, the reference to the server manager with all of its tcservers remains in the cluster database. If the connected clients use a static session discriminator (such as rich client shared sessions do), a user attempting to reconnect or log in might not be able to do so. To prevent this kind of failure, an administrator can do either of the following: Configure the rich client to use non-shared sessions. Remove the unavailable pool and its tcservers from the cluster database (for example by running mgradmin.bat -clean from a healthy server manager). Other SOA clients such as CAD clients, NX being started without rich client, rich clients with SharedSession off, or custom SOA clients with random SOA session discriminator are not affected by this limitation.