0

I have a web service implemented in ASP.NET.

I instantiate my NHibernate session in the Global.asax event handlers as follows:

    protected void Application_BeginRequest(object sender, EventArgs e)
    {
        NHibernateInitializer.Instance().InitializeNHibernateOnce(
        () => InitializeNHibernateSession());
    }

    private void InitializeNHibernateSession()
    {
        NHibernateSession.Init(
            webSessionStorage,
            new string[] { Server.MapPath("~/bin/DAL.Server.Data.dll") },
            new AutoPersistenceModelGenerator().Generate(),
            Server.MapPath("~/NHibernate.config"));
    }

My problem is, whenever I need to update the NHibernate.config connection string to connect to a different database (for testing purpose, on the deployment server) NHibernate still maintain the connection to the previously connected DB.

Only restarting IIS can resolve this problem. Does anyone have any idea if this is due to come kind of caching in IIS? or some settings I have missed out? Thanks in advance!

rm6
  • 13
  • 2

1 Answers1

1

Change in nhibernate.config file does not force restart of IIS application, that means that it keeps working with the same istance of ISessionFactory and IOC container configured.

The best is to configure nhibernate to use connection string that is stored in web.config file and referenced by name.

Another thing you can do is to move configuration of nhibernate into web.config file. Then chagning it would force reconfiguration of nhibernate.

Sly
  • 15,046
  • 12
  • 60
  • 89
  • Thanks for the answer. I realize it won't be reset as long as the Application is still using the same HttpAppilcation instance.. so recycling the Application Pool for the web application actually refreshes the NHibernate connection as well. Thanks! – rm6 Jul 24 '12 at 20:55