Hi, NhProf keeps telling me that on _some_ requests of my web app my session/transactions seem to use multiple threads, which is not an overly good thing. And my production sql server (2005) sometimes enters into a race condition, where too many requests kill it (problems with closing transactions that are already disposed of, sounding just like what you would expect from a threading issue with ISession).
Now, nowhere in my code I am even coming close to managing my threads. >From my point of view 1 thread should be all I need. I am using Monorails with castle windsor integration. My daos are created per web request, sessions come from castle's NHibernateIntegrationFacility and use Automatic Transaction Facility, so these might need my love in some way, but I cannot tell from the outside. Are there some good debug paths to find out what is wrong before I get the next server crash? I already posted this at nhusers, but did not get any real answers there, just messages from other users experiencing the same. So I try it here :). There is also the possibility of a false positive in NHProf, but I hope not so - I'd love to be able to actually see my sql server transactions bug :) Thanks, -- Jan --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Castle Project Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/castle-project-users?hl=en -~----------~----~----~----~------~----~------~--~---
