Re: WAS suddenly dying

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Hey Steven,

some more additional information: we run 16 services within one app pool. All services are going out of service at the
same time. Restarting the app pool / the site or the IIS does not help.

We are in deep need of your advice.

Thanks,
Frank


Frank Hauptlorenz schrieb:
Hi Steven,

the problem is sadly still active. We had 2 or 3 weeks without problems, but these week we had already 2 failures.

What we did recognize is, that the http pages of the services are working but we can't add the services to visual
studio projects or access them with the svcutil.exe (timeout after 5mins). After rebooting the machine (yes, only this helps)
we can add the services again (same url guaranteed).

Can you please send me your docs for analyzing "hanging" .net processes again? The urls you send are no more valid.

Thanks a lot,
Frank



Steven Cheng schrieb:
Hi Frank,

Have you got any further progress on this issue or is there anything else need help?

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead


Delighting our customers is our #1 priority. We welcome your comments and suggestions about how we can improve the support we provide to you. Please feel free to let my manager know what you think of the level of service provided. You can send feedback directly to my manager at: msdnmg@xxxxxxxxxxxxxx
------------------------------
From: stcheng@xxxxxxxxxxxxxxxxxxxx ("Steven Cheng")
Organization: Microsoft
Date: Thu, 26 Feb 2009 07:51:27 GMT
Subject: Re: WAS suddenly dying


Thanks for your reply Frank,

Yes, such kind of "lock(..){...}" block will sometimes cause deadlock if some resource(protected by a lock) is block on another lock.
Also, for the "private static object thisLock = new object();" variable here, since it's a static member object, that means all the instance of that class(I think it's your WCF service class) will share a single copy of this object(in the same .NET AppDomain). So it doesn't matter what "InstanceContext" you're using for the WCFService.

Also, inside the "lock()..." block, you're performing DataBase accessing, this also indicate that this is likely the cause. Since whenever there is resource leak on the data access resource(such as Connection), the "lock()" block may enter a deadlock state(wait on resource held by another thread).

Anyway, when you get the chance to get a hang dump next time the problem occur. YOu can use some debugging command(mentioned in those articles) to verify these things. If you have anything unclear on this, please feel free to let me know.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead


Delighting our customers is our #1 priority. We welcome your comments and suggestions about how we can improve the support we provide to you. Please feel free to let my manager know what you think of the level of service provided. You can send feedback directly to my manager at: msdnmg@xxxxxxxxxxxxxx

==================================================
Get notification to my posts through email? Please refer to http://msdn.microsoft.com/en-us/subscriptions/aa948868.aspx#notifications.




--------------------
Date: Wed, 25 Feb 2009 16:25:26 +0100
.

Quantcast