MattB

Trying to consolidate messages here. We are having a heck of a time replicating this issue in a controlled environment. Our current load testing (simple commands) via functions is working...

@twiga2013 Thanks for your info this really helps!. We were able to reproduce the problem with this configuration. What we would like to you do is this, As your using...

@mathiasbl , when using the Async messages you should not be seeing locking on any endpoint, could you clarify what your seeing?

Correct, this should not lock the channel, are you seeing that happen?

Request ID's are set via the WebAPI request's and you can see them via a fiddler trace. You can cross check the behavior by setting UseWebAPI = false on the...

As a follow up, we confirmed that the Request ID is being passed via the webAPI leg, and we are researching the server side disconnect there. If you want to...

Thanks for your report, we will have a look... for the moment, Please set client.UseWebAPI=false after you create the client. that should clear the problem for you

@0xced Is there some reason you feel that is necessary? We did that intentionally to limit the stack trace that was exported. is there something your trying to do with...

Ok so you're seeing the failure in the verbose log but not in the resulting exception. we will take a look, thanks

We are still digging at this one.. That its showing in the Log and NOT in lastexception is what is odd. The log writer is what is actually populating that...