views:

574

answers:

3

I'm running into a weird issue with my WCF Service using WS binding. When I configure it with no sessions (security/reliable) it works just fine, but not so with sessions. For example when I configure with security (message security, windows credentials), I get a timeout after 10th or 11th call. My service calls another WCF Service but, but both services are configured with same binding parameters.

How would you debug an issue like this? What tools would you use other than turning on tracing and using SvcTraceViewer?

+1  A: 

The best way to debug such scenario would be to activate tracing in the WCF service/client. The tracer creates log files which you can use the build-in trace viewer to read. http://msdn.microsoft.com/en-us/library/ms733025.aspx

dotmad
I'm awaretracing (see last paragrpah). My question was is there anything else.
aogan
Sorry, missed your comment.But why would you need another way?
dotmad
I was just wondering whether there is something else out there. Also I found that tracing is not that easy to use, especially when there are protocol (security,reliable messaging) messages are involved.
aogan
I agree that it is a pain to use the SvcTraceViewer and for some strange reason I thought the original implementation of the utility was better than it is today.
EnocNRoll
A: 

Sounds like you may be hitting a throttle...

http://stackoverflow.com/questions/480020/wcf-service-throttling

http://kennyw.com/indigo/150

Brian
+2  A: 
EnocNRoll
Closing of session is the first area I looked since I'm aware of the session throttling settings which is mention above. Also, I agree most of the issues turn out to be configuration related.
aogan
So, have you ruled out session problems? What makes you believe it is not related? Has increasing the throttling settings allowed for more connections?
EnocNRoll