2014/1/21 Ian Harden <[email protected]> > We have a WCF service that runs on the same server as the web site. >
The statement below where you speak of the site hanging makes me confused. It's clear that you have a single server, but please clarify if the "services" and the "website" run inside the same or separate IIS sites. If it's the same site, is it then the same or different virtual applications? > We had to turn on aspNetCompatibilityEnabled to get at the HttpContext, > we had to turn this on because the services use the same functions as the > website to save and retrieve data. The problem is that since we have added > the services the site hangs up every few days now. Are there any > recommendations to solve this issue? As a worst case we could break them > apart but since they are doing the same thing I would like to leave them as > is if possible. > Sorry, there is no magic solution. You just have to dig in and figure out where it's hanging: How does it hang? Where in the code does it hang? Have you enabled log4net logging? Do you use logging in your request handing code so that you can see in the logs how far the request handling progress before it gets stuck? Do you use any threading constructs or concurrency control features like lock, ManualResetEvent and similar, etc.? Do you have singletons or other shared state where you aren't but should be using some sort of locking? Run the site in with debugging symbols present and attach the visual studio debugger? Or Windbg - lightweight but more difficult. /Oskar -- You received this message because you are subscribed to the Google Groups "nhusers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/nhusers. For more options, visit https://groups.google.com/groups/opt_out.
