WCF, Only 1 of 3 processes handles requests

Question

0.00/5 (No votes)

See more:

, +

I am ignorant on WCF, and the guy who is smart, isn't.:~

2k8, 64 bit, standard, 16 GB, quad, hyperthreaded
A service with 3 processes, 2 at start up, each process has a single thread.
2 processes come up, using cpu and memory.
5 people running our client.
Process 3 comes up when requests start.

Processing a call takes 5-10 minutes.
All calls to the server lock the server object on the server side.

The three processes continue for a while.
Two of them stop processing, while one continues.
When the one finishes, another starts processing, and the one locks.

I believe that object.lock is local, not a mutex.
I believe that IIS processes do not share memory.

But it sure looks like the lock is operating across processes.
We are taking the lock out on Monday, to see what happens.

Is this an issue that rings a bell for anyone?
Thanks RM

Posted 26-Mar-10 14:34pm

RichardM1

Add a Solution

2 solutions

Solution 2

Response to Ahmed.
You are right, it was a resource issue.
All server calls are synchronous/blocking.
The server was making calls back through to itself as a client.
When a process called the same SO, that process locked.
It took one of the processes out of the pool until it returned.
But it also called itself as a client, blocking another.
Pretty soon, all the processes are blocked.
Waiting for one to finish so they can process.
Classic deadlock. :rolleyes: :-O

Posted 15-Apr-10 15:56pm

RichardM1

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

TheGreatAndPowerfulOz · Accepted Answer · 2010-04-15T15:36:00

I am familiar with WCF, but not under IIS.

However, I have run into similar situations which turned out to be either a db table being locked by a long-running process or a particular stored procedure returning 3 million rows and causing the .Net process to abort with an out-of-memory exception.

Also, if any thread in .Net process throws an unhandled exception that will cause the process to end. Look for strange-looking events in the system event log.

without more info, I'm guessing.