ws reliablemessaging - WCF ReliableSession and Timeouts -
I have a WCF service which is primarily used to manage documents in a repository.
I used Chanqing channel sample from MS that I can upload / download large files.
Now I have implemented a reliable session with the service and I am seeing some strange behavior.
I am using the time-period value here.
This.SendTimeout = New TimeSpain (0, 10,0); this. Opentimeout = new timespan (0, 1, 0); This.CloseTimeout = New TimeSpain (0, 1, 0); This.ReceiveTimeout = New TimeSpain (0, 10, 0); Trustworthy B.E. activityTimeout = New TimeSpain (0,2,0);
I have the following problems:
1 If the service is not there;
I tried to do this with my test client.
Scenario 1: Without a trusted session: I get the following exception: Could not connect to net.tcp: // local host: 8788 / Media management service / AP1 Connection attempt lasted for a time period of 00: 00: 00.9848790. TCP error code 10061: No connection can be made because the target machine has actively denied 127.0.0.1:8788
This is the correct behavior because I have given OpenTime as 1 second .
Scenario 2: With Trusted Session:
I get the same exception:
Could not connect to net.tcp : // Local Host: 8788 / Media Management Service / AP1. Connection attempt lasted for a time period of 00: 00: 00.9692460. TCP error code 10061: No connection can be made because the targeted machine has actively denied it from 127.0.0.1:8788.
But this message comes after about 10 minutes. (I believe that after SendTimeout) here I have enabled the trusted session and now it looks like OpenTimeout = SendTimeout for the customer. Is this the desired behavior?
2: Issue while uploading large files with reliable sessions:
The general rule is to set a big value for maximum reciprocity, sendtime, and receiver timeout Have to do.
But in the case of channel channeling, the size of the maximum received message is not sent as data.
So I have set and received a huge price for the timeout: say 10 hours now the upload is recovering, but it has a side effect, even if the service does not end, (1) the behavior described in Due to customer connection 10 hours from time to time
Please tell me your thoughts on this behavior.
Comments
Post a Comment