ws-reliablemessaging

在互联网世界中，由于软件，网络，机器等各种无稳定因素，一个SOAP消息可能会发生传输失败。如果这是一个天气预报的消息，那么失败还不会造成太大影响，但如果消息是有关银行操作，比如转账，消息的传输不可靠就可能会导致用户的损失。 因为上述原因，WS-ReliableMessaging和OASIS标准，规定了一个模块化机制，确保消息传输的可靠性。 消息在源与目的地之间，消息一定有且仅有一次传递成功。也可以规定消息最少传递一次。 消息可以存在顺序性。 消息的时效性。 接下来，我将使用Metro框架来实现可靠消息。 Metro的安装 首先，若想使用Metro引擎，就必须先安装Metro。Metro的安装步骤可以从 https://metro.java.net/guide/ch02.html#mustanga3 找到。 开启可靠消息 开启可靠消息的方法很简单，基于之前开发webservice的步骤，开启可靠消息只需要修改server端。开启方法有两种： 使用WSIT配置文件，声明policy 直接在WSDL中声明policy policy如下： <definitions ....> <wsp:Policy wsu:Id="NewWebServicePortBindingPolicy" xmlns:wsrmp="http://docs.oasis-open.org/ws-rx/wsrmp

For experiments, I created a simple "Hello World" WCF service and client using .NET 4.5 on VS2012. The server is hosted on a console application and use net.tcp binding. I wrote the client code to send a burst of async requests (a total of 700 requests) to the server. Everything went fine until I turned ON the Reliable session feature of the service. After it is ON, the service suddenly ran very slow and it took almost a minute on my machine to complete the 700 requests. I tried to fine tune the Concurrency and Throttling parameters (see below) but it didn't help. Does anyone know why this

When using a WSHttpBinding in WCF with reliableSessions enabled, my service reference updates itself to: <reliableSession ordered="true" inactivityTimeout="00:10:00" enabled="true"> </reliableSession> I cannot add the maxRetryCount attribute to the reliableSession as long as the binding is configured as a WSHttpBinding. Now my question: what is the value of maxRetryCount when using a WSHttpBinding, and is there any way to change this in config; without the use of a CustomBinding? You cannot set the maxRetryCount on a standard wsHttpBinding configuration. In order to set that value, you need to