When we are deployed to a testing environment. the Dataportal can become unresponsive and appears to be hung. We noticed that Dr. Watson was running as an IIS app pool identity, eating about 15-25% of CPU. We also noticed that all app pools could be stopped gracefully except the one that the CSLA portal runs under.
We are using the WCF Dataportal.
Can anyone give me things to check for that might cause this behavior. Has anyone else expirenced this? We don't see this locally of course.
Thanks.
Copyright (c) Marimer LLC