When using Unshared State Connections with clients, how should the EMS Servers be configured?
Article ID: KB0088642
Updated On:
| Products | Versions |
|---|---|
| TIBCO Enterprise Message Service | - |
| Not Applicable | - |
Description
Resolution:
Description:
= = = = = = =
When using Unshared State Connections with clients, how should the EMS Servers be configured?
Environment:
= = = = = = =
ALL
Resolution:
= = = = = =
- Reference Chapter 19 Fault Tolerance : Unshared State Failover Process.
The Unshared State Failover client provides the ability to connect to one EMS server and if that server connection is broken, it will connect to a new EMS server.
The Unshared State Failover client reinitializes all the client objects when it successfully connects to a new server so that the application can continue to use those objects.
Configuration of unshared state FT in EMS is just like configuring two standalone EMS servers, and each EMS server uses different data store files or database.
You should make sure that any EMS server configuration changes should be applied to all EMS servers.
Producers that use the Unshared State Failover should catch failures on send that may occur during a failover and resend the affected message. As this may lead to duplicate or out-of-order messages, the corresponding client consumers should be equipped to filter out duplicates and re-order messages if dictated by the application requirements.
In addition, since EMS servers are running at the same time, and in this case there could be a possibility where some clients are connected to one EMS server and other clients connected to the EMS server. In such a situation, applications should be able to tolerate those behavior.
Description:
= = = = = = =
When using Unshared State Connections with clients, how should the EMS Servers be configured?
Environment:
= = = = = = =
ALL
Resolution:
= = = = = =
- Reference Chapter 19 Fault Tolerance : Unshared State Failover Process.
The Unshared State Failover client provides the ability to connect to one EMS server and if that server connection is broken, it will connect to a new EMS server.
The Unshared State Failover client reinitializes all the client objects when it successfully connects to a new server so that the application can continue to use those objects.
Configuration of unshared state FT in EMS is just like configuring two standalone EMS servers, and each EMS server uses different data store files or database.
You should make sure that any EMS server configuration changes should be applied to all EMS servers.
Producers that use the Unshared State Failover should catch failures on send that may occur during a failover and resend the affected message. As this may lead to duplicate or out-of-order messages, the corresponding client consumers should be equipped to filter out duplicates and re-order messages if dictated by the application requirements.
In addition, since EMS servers are running at the same time, and in this case there could be a possibility where some clients are connected to one EMS server and other clients connected to the EMS server. In such a situation, applications should be able to tolerate those behavior.
Issue/Introduction
When using Unshared State Connections with clients, how should the EMS Servers be configured?
Feedback
Yes
No
Powered by
