A Follow-up on PIAB+WCF Integration

re: A Follow-up on PIAB+WCF Integration

Hugh Ang — Wed, 16 Jan 2008 20:51:51 GMT

Tom,

Have you found anything yet on the issue? You might want to run adplus to capture crash dumps. I will try to repro in a week or so once I am code complete with my cuurent project. At this point, I am suspecting that this was caused by the default interception mechanism implemented by PIAB, which uses the .NET remoting proxy.

Hugh

re: A Follow-up on PIAB+WCF Integration

tomholl — Thu, 17 Jan 2008 00:41:59 GMT

Hey Hugh -

I'm still working on getting a repro outside of my customer project so I can share it. Now that my project is unblocked this has become a spare time activity, but I'm making some progress.

Your assessment that it's related to the .NET Remoting proxies sounds accurate, as the exceptions I was getting were thrown from those classes. Still there must be something in the combination of WCF and PIAB which is causing the instability in this scenario.

I'll keep you in the loop with what I learn.

Tom

.NET Middle Tier Work

Loosely Coupled Human Code Factory — Fri, 08 Feb 2008 23:54:27 GMT

A recent topic that has come up in discussion is pieces of middle tier patterns and libraries. ...

re: A Follow-up on PIAB+WCF Integration

kolaan — Mon, 18 Feb 2008 16:32:56 GMT

Hi Tom,

At one of my customers we have a problem that looks similar to the problem you have. We used the sample provided in the article in MSDN magazine and implemented it in our WCF services.

Instead of a Fatal Execution Engine Exception, we get a System.Reflection.TargetException. When we run every WCF service in its own application pool, this problem doesn't occur.

Koen Laan