简体   繁体   English

WCF和MsmqBinding到远程专用队列

[英]WCF and MsmqBinding to remote private queue

We have a WCF log service that uses MsmqBinding and WAS. 我们有一个使用MsmqBinding和WAS的WCF日志服务。 The issue is that I try to use it from remote computer and that message seems to never reach the destination queue. 问题是我尝试从远程计算机使用它,并且该消息似乎永远不会到达目标队列。 Here are the facts : 这是事实:

  1. Server config 服务器配置
    • List item 项目清单
    • destination machine name : logserver.domain.ext 目标计算机名称:logserver.domain.ext
    • destination queue : private$/logservice.svc (journaling enabled) 目标队列:private $ / logservice.svc(启用日记功能)
    • security on the queue : everyone : full control, NETWORK SERVICE : Full Control 队列中的安全性:所有人:完全控制,网络服务:完全控制
    • IgnoreOSNameValidation registry key : set IgnoreOSNameValidation注册表项:设置
  2. Client config 客户端配置
    • client endpoint address : logserver.domain.ext/private/logservice.svc 客户端端点地址:logserver.domain.ext / private / logservice.svc
  3. Observed behaviour 观察到的行为
    • the output queue is well created ans has status Connected and 0 message wainting 输出队列创建良好,状态为Connected,0消息正在等待
    • if I pause the output queue, I see messages appearing and then desapearing when resume the queue 如果我暂停输出队列,则恢复队列时会看到消息出现然后消失
    • no message can be seen in the remote queue or the journal 在远程队列或日记中看不到任何消息

and the worth is : 价值是:

var queue = new MessageQueue(@"FormatName:DIRECT=OS:logserver.domain.ext\private$\logservice.svc");
queue.Send("hello");

works ! 工程!

You do not mention permissions for the ANONYMOUS LOGON account. 您没有提及“匿名登录”帐户的权限。 This is the account that remote private queue access will happen under if you are not explicitly using Windows security on the binding. 如果您未在绑定上明确使用Windows安全性,则将使用该帐户进行远程专用队列访问。

I was facing the same issue, and it turned out that the issue was with Distributed Transaction Coordinator configuration. 我遇到了同样的问题,事实证明该问题与分布式事务处理协调器配置有关。 This MSDN document helped me solve it. 这个MSDN文档帮助我解决了这个问题。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM