Closed vladimirlapacek closed 9 years ago
From the stack it looks like the request is making its way all the way into our Web API layer to handle a request, but something we're using from Web API has already been disposed (for some reason).
Yea, that's a head-scratcher as it's not obvious why this HttpMessageInvoker has been disposed.
Is there any way how I can learn about what is causing this?
I think that I have always seen these exceptions, but only during the initial call after the app pool recycle.
I don't have any additional insights into the problem. Sorry.
Has anything ever come of this?
I am getting the ObjectDisposedException after an app pool cold start quite consistently. I would like to debug it somehow, but am not really sure where to start. We are using haproxy for load balancing and Chrome for hitting the IIS, which hosts this IS3 instance (v 2.0.1).
Any hints are greatly appreciated.