服务代理冻结应用程序
本文关键字:应用程序 冻结 代理 服务 | 更新日期: 2023-09-27 18:27:28
这是我遇到的一个完全不知道的问题。我定义了一个IWorkerServiceContract类,如下所示:
[ServiceContract]
public interface IWorkerServiceContract
{
[OperationContract]
int Test(int test);
}
没什么特别的,我只是想测试连接。这是我的服务等级:
class WorkerService : IWorkerServiceContract
{
public static ILogger Logger { get; set; }
public int Test(int test)
{
return test + 1;
}
public static ServiceHost Listen(Uri baseAddress)
{
ServiceHost host = new ServiceHost(typeof(WorkerService), baseAddress);
try
{
host.Open();
Logger.WriteLine("Listening at address: " + baseAddress.ToString());
}
catch (Exception e)
{
Logger.WriteLine("An exception was thrown, reason: {0}", e.Message);
}
return host;
}
}
logger对象是由初始化器类实例化的,它基本上记录到使用AllocConsole()分配的控制台。当我调用Listen()时,一切都很好,我可以通过WCF测试客户端进行连接,并远程调用test()方法。尽管,当我定义代理时:
public partial class WorkerProxy : ClientBase<IWorkerServiceContract>,
IWorkerServiceContract
{
public WorkerProxy(EndpointAddress remoteAddress) :
base("workerEndpoint", remoteAddress)
{ }
public WorkerProxy(Uri remoteAddress) :
base("workerEndpoint", new EndpointAddress(remoteAddress))
{ }
public WorkerProxy(string remoteAddress) :
base("workerEndpoint", new EndpointAddress(remoteAddress))
{ }
public int Test(int test)
{
return base.Channel.Test(test);
}
}
并使用以下代码:
WorkerService.Listen("net.tcp://localhost:19000/dcalc");
WorkerProxy wp = new WorkerProxy("net.tcp://localhost:19000/dcalc");
wp.Test(0);
应用程序冻结!这是我的app.config文件:
<?xml version="1.0"?>
<configuration>
<system.serviceModel>
<bindings>
<wsHttpBinding>
<binding messageEncoding="Mtom" maxReceivedMessageSize="10485760">
<readerQuotas maxArrayLength="10485760" />
</binding>
</wsHttpBinding>
<netTcpBinding>
<binding maxReceivedMessageSize="10485760">
<readerQuotas maxArrayLength="10485760" />
</binding>
</netTcpBinding>
</bindings>
<services>
<service name="DCalc.Manager.ManagerService" behaviorConfiguration="managerServiceBehavior">
<endpoint address="" binding="wsHttpBinding" contract="DCalc.Common.IManagerServiceContract"/>
<endpoint address="mex" binding="mexHttpBinding" contract="IMetadataExchange"/>
</service>
<service name="DCalc.Worker.WorkerService" behaviorConfiguration="workerServiceBehavior">
<endpoint address="" binding="netTcpBinding" contract="DCalc.Common.IWorkerServiceContract"/>
<endpoint address="mex" binding="mexTcpBinding" contract="IMetadataExchange"/>
</service>
</services>
<client>
<endpoint address="" binding="netTcpBinding" contract="DCalc.Common.IWorkerServiceContract" name="workerEndpoint" />
<endpoint address="" binding="wsHttpBinding" contract="DCalc.Common.IManagerServiceContract" name="managerEndpoint" />
</client>
<behaviors>
<serviceBehaviors>
<behavior name="managerServiceBehavior">
<serviceMetadata httpGetEnabled="true" policyVersion="Policy15"/>
<serviceDebug includeExceptionDetailInFaults="true" />
</behavior>
<behavior name="workerServiceBehavior">
<serviceMetadata policyVersion="Policy15"/>
<serviceDebug includeExceptionDetailInFaults="true" />
</behavior>
</serviceBehaviors>
</behaviors>
</system.serviceModel>
</configuration>
我不明白的是,正如你所看到的,我已经定义了一个ManagerService,应用程序可以毫无问题地连接到它。这似乎不是协议问题,我在wsHttpBinding中得到了同样的结果。
我做错了什么?
您看到应用程序被冻结的原因是线程死锁,这意味着两个线程在执行部分代码/访问公共资源时会相互锁定。
在这种情况下:
在客户端,当工作代理线程调用Test(0)
时,它将等待响应返回。
在"服务器端",服务器线程同时尝试控制并返回结果。由于两个线程之间的线程相关性,服务器线程将等待工作线程完成,但工作线程正在等待响应,因此它们都无法继续,从而发生死锁。