I have a project that I use Fluent NHibernate and StructureMap on, and I am seeing a SQL "Timeout expired" exception thrown during what I assume is the Application_Start stage of my application. Basically, the first two or three times I hit the site after some builds, I get an error from StructureMap about receiving an exception when trying to build the ISession instance, which is just essentially configuring Fluent NHibernate.
It's not a huge deal for me when I am developing, as I just reload the page a few times and it comes up, and I don't see it again until one of my builds triggers it. What I'm worried about is when I finally deploy this, I don't want to see this happening. Can anyone think of a reason that I might be seeing this behavior? It says it is timing out, which I would think means that it can't communicate with the SQL server, and the only thing I can think of that might be doing this would be if the application was holding a connection open post Application_Start and the rebuild severed this connection and the SQL server refused to open a new connection until that first one timed out or something. I'm kind of at a loss for what's happening, and don't know where to look. / Michael / -- You received this message because you are subscribed to the Google Groups "Fluent NHibernate" group. To post to this group, send email to fluent-nhibern...@googlegroups.com. To unsubscribe from this group, send email to fluent-nhibernate+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/fluent-nhibernate?hl=en.
