是否TIBCO EMS服务器重新连接管理?或者做客户端? [英] Does the TIBCO EMS server manage reconnection? or does the client?

查看:361
本文介绍了是否TIBCO EMS服务器重新连接管理?或者做客户端?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

在TIBCO EMS .NET参考指南说(第134)

The TIBCO EMS .NET reference guide says (pg 134)

要允许连接行为和容错性,对的serverURL参数必须是用逗号分隔的两个或两个以上的URL列表。在只有一台服务器的情况下,你可能会提供该服务器的URL的两个副本,使客户端重新连接(例如,TCP://本地主机:7222,TCP://本地主机:7222)。

To enable reconnection behavior and fault tolerance, the serverURL parameter must be a comma-separated list of two or more URLs. In a situation with only one server, you may supply two copies of that server’s URL to enable client reconnection (for example, tcp://localhost:7222,tcp://localhost:7222).

TIBCO EMS用户指南(第292)谈论故障转移方案,客户端通知和客户端的自动转移到备份服务器,但没有明确重新连接有关。

The TIBCO EMS user's guide (pg 292) talks about failover scenarios, client notification, and automatic transfer of clients to the backup server, but nothing specifically "reconnect" related.

在一个重新连接的设想,并在服务器处理一切?或者客户是否必须做一些与它的TIBCO.EMS.Connection实例?

In a "reconnect" scenario, does the server handle everything? or does the client have to do something with it's TIBCO.EMS.Connection instances?

推荐答案

这看上去像是从我们的测试中,该有是在服务器和客户端,使此功能上都设置。在客户端,SetReconnAttemptCount,延迟,超时管理客户端尝试重新连接,一旦它意识到服务器故障切换/连接故障切换的尝试。

Looks like from our testing that the there are settings on both the server and the client that enable this feature. On the client side, the SetReconnAttemptCount, Delay, Timeout govern the attempts the client tries to reconnect once its aware of a server failover / connection failover.

在我们的测试中,我们使用单一服务器环境中,在连接字符串中列出的服务器的两倍(使用你上面列出的伎俩),当该服务器脱机,我们收到的故障转移过程回吐的客户通知影响(我们启用Tibems.SetExceptionOnFTSwitch(真) )和服务器恢复联机时,我们的客户无缝地重新连接没有丢失一个节拍。我们并不需要任何代码,内部重新连接逻辑发挥了奇效。

In our testing, we used a single server environment, listed the server twice in the connection string (using the trick you outlined above) and when that server was taken offline, we received a client notification of the failover process taking affect (we enabled Tibems.SetExceptionOnFTSwitch(true)) and when the server was brought back online, our client seemlessly reconnected without missing a beat. We didn't need to code anything, the internal reconnect logic worked its magic.

在服务器端,需要容错启用,我相信服务器和客户端客户端 - 服务器心跳需要启用(尽管这尚未得到验证)。

On the server side, fault tolerance needs to be enabled and I believe server-client and client-server heartbeats need to be enabled (though this has not yet been verified).

希望这有助于。

这篇关于是否TIBCO EMS服务器重新连接管理?或者做客户端?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆