CODEWITHSUNDEEP
wcf
zhiyuan_
zhiyuan_

Reputation: 197

WCF IsOneWay = true report Exception

[ServiceContract]
public interface Service
{
   [OperationContract(IsOneWay = true)]
   void ServiceMethod();
}

I set server's code with IsOneWay = true, because the client does not care about the server's result and the server's method may need run a long time (e.g.30 mins) in some cases.

But I found the client still waits for the server's method to be finished. After the server finished in 30 mins, client requests again, report the CommunicationException:

"The socket connection was aborted. This could be caused by an error processing your message or a receive timeout being exceeded by the remote host, or an underlying network resource issue. Local socket timeout was '00:01:00'".

I think the client still wait the result (default receiveTimeOut is 10 mins), then lead to timeout. I use WCF 3.0.

Can you help me? Thank you!

Upvotes: 2

Views: 1409

Answers (3)

tom redfern
tom redfern

Reputation: 31760

A one-way call in WCF is not the same thing as an asynchronous call.

Even though the client making a one-way call will not receive a response from the service, if the service does not have a thread available to dispatch or queue the incoming client request then the client will hang and eventually timeout if no dispatcher thread becomes available within the timeout period.

The number of available threads and the size of the request queue are managed by WCF and are determined by the service concurrency mode, session mode, and whether the service was configured with reliable messaging, amongst other factors.

Upvotes: 2

Ricibob
Ricibob

Reputation: 7705

MSDN ServiceBehviorAttribute.concurrencyMode states:

Setting ConcurrencyMode to Single instructs the system to restrict instances of the service to one thread of execution at a time, which frees you from dealing with threading issues.

That means that server side all calls on the service will come in on a unique thread. Which is great as you don't have to worry about multithreading but also not so great in that if you block that one thread with a long operation then other calls from your client that happen while its processing will not get through. Hence the exception.

ConcurrancyMode = Single is the default. You could try setting the concurrancy mode to Multiple - which will mean that calls will now come in on random threadpool threads and if one of those is busy processing a request another one is available for another request. But because the enviroment is now multithreading you will have to protect server objects from access by multiple thread with locks or other syncronisation mechanisms.

Upvotes: 1

DaveRead
DaveRead

Reputation: 3413

Have you tried re-generating the service client? It may be that the client still has a reference to a synchronous operation, whereas the server has been re-defined as one way / async.

Upvotes: 0

Related Questions