Hum..Strange behavior I have seen..(BTW, as I said I am using Ent Lib 5.0) at some point..
Type : System.InvalidOperationException, mscorlib, Version=126.96.36.199, Culture=neutral, PublicKeyToken=b77a5c561934e089 Message : 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.
Source : System.Data
Help link :
Data : System.Collections.ListDictionaryInternal
TargetSite : System.Data.ProviderBase.DbConnectionInternal GetConnection(System.Data.Common.DbConnection)
Stack Trace : at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
at Microsoft.Practices.EnterpriseLibrary.Data.Database.GetNewOpenConnection() in e:\Builds\EntLib\Latest\Source\Blocks\Data\Src\Data\Database.cs:line 1176
at Microsoft.Practices.EnterpriseLibrary.Data.Database.GetWrappedConnection() in e:\Builds\EntLib\Latest\Source\Blocks\Data\Src\Data\Database.cs:line 1200
This error was basically from Execute method from below in my code.
DataAccessor<...> da = db.CreateSprocAccessor<...>(sp,
pEntities = da.Execute(
I deployed my web application to IIS(5.1) hosted in Windows XP Prof.
As far as I know, this pool error message is database related error message....However, it seems that whenever I restarted the IIS, it looks like this pool issue went away.
How could this happen? I didn't restart the SQL server, but I just restarted the IIS, which means...I think that pool connection issue should still remain regardless of IIS restart..am I wrong?
Also my SQL script doesn't take long time at all....
1. Is there any way that I can explicitly close the connection for Execute method?
2. Could you explain me a bit if you can, how this pool error message went way whenever I restarted the IIS? I think IIS should not be matter of this error.