WCF 回调通道出现故障

发布于 2024-08-07 09:46:08 字数 1367 浏览 8 评论 0原文

我正在尝试为 wcf 客户端实现重新连接逻辑。我知道您必须在当前通道进入故障状态后创建一个新通道。我在通道故障事件处理程序中执行了此操作:


internal class ServiceClient : DuplexClientBase, IServiceClient
{
  public ServiceClient(ICallback callback, EndpointAddress serviceAddress)
   : base(callback, MyUtility.GetServiceBinding("NetTcpBinding"), serviceAddress)
  {
   // Open the connection.
   Open();
  }

  public void Register(string clientName)
  {
    // register to service
  }

  public void DoSomething()
  {
    // some code
  }
 }

 public class ClientApp
 {
  private IServiceClient mServiceClient;

  private ICallback mCallback;

  public ClientApp()
  {
   mServiceClient = new ServiceClient( mCallback, new EndpointAddress("someAddress"));

   mServiceClient.Register();

   // register faulted event for the  service client
   ((ICommunicationObject)mServiceClient).Faulted += new EventHandler(ServiceClient_Faulted);
  }

  void ServiceClient_Faulted(object sender, EventArgs e)
  {
   // Create new Service Client.
   mServiceClient = new ServiceClient( mCallback, new EndpointAddress("someAddress"));

   // Register the EI at Cell Controller
   mServiceClient.Register();
  }

  public void DoSomething()
  {
   mServiceClient.DoSomething();
  }
 }

但在我的单元测试中,我仍然收到“通信对象 System.ServiceModel.Channels.ServiceChannel 无法用于通信,因为它处于故障状态”异常。

是否有可能回调通道仍然存在故障,如果是,如何更换回调通道?

I'm trying to implement a reconnect logic for a wcf client. I'm aware that you have to create a new channel after the current channel entered the faulted state. I did this in a channel faulted event handler:


internal class ServiceClient : DuplexClientBase, IServiceClient
{
  public ServiceClient(ICallback callback, EndpointAddress serviceAddress)
   : base(callback, MyUtility.GetServiceBinding("NetTcpBinding"), serviceAddress)
  {
   // Open the connection.
   Open();
  }

  public void Register(string clientName)
  {
    // register to service
  }

  public void DoSomething()
  {
    // some code
  }
 }

 public class ClientApp
 {
  private IServiceClient mServiceClient;

  private ICallback mCallback;

  public ClientApp()
  {
   mServiceClient = new ServiceClient( mCallback, new EndpointAddress("someAddress"));

   mServiceClient.Register();

   // register faulted event for the  service client
   ((ICommunicationObject)mServiceClient).Faulted += new EventHandler(ServiceClient_Faulted);
  }

  void ServiceClient_Faulted(object sender, EventArgs e)
  {
   // Create new Service Client.
   mServiceClient = new ServiceClient( mCallback, new EndpointAddress("someAddress"));

   // Register the EI at Cell Controller
   mServiceClient.Register();
  }

  public void DoSomething()
  {
   mServiceClient.DoSomething();
  }
 }

But in my unit test I still get a "The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state" exception.

Is it possible that the callback channel is still faulted and if yes how can I replace the callback channel?

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(2

蓦然回首 2024-08-14 09:46:08

到目前为止,我经历过 WCF 连接出现故障时需要重新创建 - 似乎没有办法恢复它。至于当发生故障时,该方法似乎可以正常触发,但通常它会在当前请求正在执行时触发并清理 WCF 连接(建立一个新连接等) - 导致失败 - 特别是在超时时。

一些建议:
- 如果与超时相关,请跟踪上次调用的时间以及包含超时值的常量。如果 WCF 连接由于不活动而被断开,请在通过线路发送请求之前断开并重新创建它。
- 另一件事,看起来您没有重新添加故障处理程序,这意味着第一个故障将得到处理,但第二次发生故障时,它将在没有处理程序的情况下失败,因为没有附加新的处理程序。

希望这有帮助

so far I have experienced that a WCF connection needs to be recreated on fault - there doesn't seem to be a way to recover it otherwise. As for when a fault occurs, the method seems to fire fine, but often it fires and cleans up the WCF connection (establishing a new one, etc) as the current request is going through - causing this to fail - especially true on timeouts.

A couple of suggestions:
- If it is timeout related, keep track of the last time a call was made and a constant containing the timeout value. If the WCF connection will have been dropped due to inactivity, drop it and recreate it before you send the request over the wire.
- The other thing, it looks like you are not re-adding the fault handler, which means the first fault will get handled, but the second time it faults it will fall over without a handler cause no new one has been attached.

Hope this helps

━╋う一瞬間旳綻放 2024-08-14 09:46:08

您是否尝试通过在Faulted事件处理程序中调用mServiceClient.Abort来重置通信通道?

编辑:

我发现您没有在恢复代码中重新初始化 mCallback 对象。您可能需要将其分配给新实例。

Have you tried to reset the communications channel by calling mServiceClient.Abort in the Faulted event handler?

Edit:

I see that you do not reinitialize the mCallback object in your recovery code. You may need to assign it to a new instance.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文