What should the client do when the TIBCO EMS server tries to switch to another resource?

TIBCO EMS User Guide (p. 292) says:

The backup server will operate indefinitely , so either A) becomes the primary server or B) connect to the main server. He also says that customers can receive a failure notification on a successful switch (see also TIBCO EMS.NET pg 220 link).

I have some questions related to these facts ...

  • What errors occur on the client side when the servers try to intercept or reconnect?

  • What is the appropriate response from the client?

    • Get new Connection objects from ConnectionFactory until done?
    • Wait for the failure message? (current connections currently established? or do I need to get a new instance?)

I hope the script is clear, any relevant information or advice will be appreciated as well.

+3
source share
2 answers

I can at least answer # 1 above.

If you enabled Tibems.SetExceptionOnFTSwitch (true); and set up an exception handler to capture messages sent by the server to the client, you will see the following:

For single-server failures with a fail-safe connection: "Connection completed."

For fail-safe connection failures: "Connection completed fail-safe switch to"

TIBCO.EMS.IllegalStateException " ".

№ 2 , , EMS . EMS, , , , , . , , , , , ems . . , , , . , , .

, , , EMS - , ( ) .

+4

TEMS (Tibco EMS - Tibco WCF). , . , , , , . , 1.2, 1.1, , .

0

Source: https://habr.com/ru/post/1698686/


All Articles