Automatic re-connection to database after DB is back again?
Hi
We experience the following issues with our Umbraco installation (4.11.6, MySQL)
If for any reason the DB goes down, Umbraco does not restore the connection automatically fter the DB is up again.
The repeated message in the log is:
MySql.Data.MySqlClient.MySqlException (0x80004005): error connecting: Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached.
(the increasing of pool size in the connection string does not help)
It describes typical scenario of leaked connections, causing such error.
The scenario is: the application opens a new connection, tries to execute some query and then closes the connection, but if the query fails, then the connection is not closed.
so this is a specific application problem not the .NET one.
Automatic re-connection to database after DB is back again?
Hi
We experience the following issues with our Umbraco installation (4.11.6, MySQL)
If for any reason the DB goes down, Umbraco does not restore the connection automatically fter the DB is up again.
The repeated message in the log is:
MySql.Data.MySqlClient.MySqlException (0x80004005): error connecting: Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached.
(the increasing of pool size in the connection string does not help)
Please advise.
Hey Gleb,
Wouldn't this be a .NET issue (connection pooling), rather than an Umbraco one?
Rich
You can have a look at the article
http://blogs.msdn.com/b/angelsb/archive/2004/08/25/220333.aspx
It describes typical scenario of leaked connections, causing such error.
The scenario is: the application opens a new connection, tries to execute some query and then closes the connection, but if the query fails, then the connection is not closed.
so this is a specific application problem not the .NET one.
is working on a reply...