WCF Service hangs on the 14th call

I'm having a problem where the WCF service hangs after 13-14 asynchronous process calls from the client. This occurs all the time. The client is a mobile JavaFX app. There is no specific error outputted in the server as well as in client. Someone suggested that it might be a throttling issue.

I've set the service side .config parameters maxConcurrent calls from 10 to 500

<serviceThrottling maxConcurrentCalls="500"开发者_Go百科  maxConcurrentSessions="500” />

So this means, it should be able to accept more than 10 calls, right? However, it didn't resolve this issue. Still hangs on the 13-14th process call.

Only one client is connecting to this web service.

What do you think is wrong?

Do you close the client after doing your call? When I encountered this problem, I did not close it, and the open requests blocked the service after a short time.

Edit: Ok, I know nothing about JavaFX =) The code below is C#, sorry. But you can surely do something similar.

Use either

WcfClient client = new WcfClient()
// ...
client.Close()

or

using(WcfClient client = new WcfClient()){
// ...
}

Similar problem here - I have an app calling from one process to another, locally, named pipes.

Calls are really light in code- basically takex an array of serializable objects, queues them on other side. Occasionally it hangs. Restarts afte rtimeout. no data lost, but... as the data is financial data, and the receiving app an autoamted trading system, that may result in very bad financial issues. Not been able to reproduce it yet.

This could very easily be caused by any deadlock condition in your code. If your service locks up and starts eating up 100% or CPU you have a dead lock. Create a dump file and see where your code was at.

I ran into the same issue my first WCF app it was a dictionary that i wasn't making sure was synchronized in logging code.

The SvcTraceViewer is super helpful in figuring out tough wcf