I have two WCF services configured as Windows Services for both client and server that perform file transfers for DR replication. I'm using chunked streaming with a wsHttpBinding.
One of the files I am testing with is 58MByte, and after it has been going for 5 miinutes it throws a stale message exception
System.ServiceModel.Security.MessageSecurityException: The security timestamp is stale because its expiration time ('2010-10-07T20:36:25.322Z') is in the past. Current time is '2010-10-07T20:44:34.155Z' and allowed clock skew is '00:05:00'.
The problem is not clock skew because the two servers are within a minute of each other, and the transfer proceeds just fine until it reaches the 5 minute mark. It's comparing the time at the beginning of the transfer to current time. If got
the receiveTimeOut set to 59 minutes.
I've seen posts about creating a custom binding to increase the clockSkew tolerance, but this seems to be more of a timeout issue.
// get the stream from the remote server, copy it to a local file stream.
stream1 = client.Get
View Complete Post