Rank: Enthusiast
Joined: 8/17/2007 Posts: 12
|
I'm having this error after publish 143 items.
the error is this:
Server Error in '/' Application. 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. Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.InvalidOperationException: 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 Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
[InvalidOperationException: 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.] System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) +1255253 System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) +105 System.Data.SqlClient.SqlConnection.Open() +111 Microsoft.ApplicationBlocks.Data.SqlHelper.PrepareCommand(SqlCommand command, SqlConnection connection, SqlTransaction transaction, CommandType commandType, String commandText, SqlParameter[] commandParameters) +33 Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(SqlConnection connection, SqlTransaction transaction, CommandType commandType, String commandText, SqlParameter[] commandParameters, SqlConnectionOwnership connectionOwnership) +48 Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(SqlConnection connection, CommandType commandType, String commandText) +15 umbraco.BusinessLogic.User.getAll() +91 umbraco.cms.businesslogic.workflow.Notification.GetNotifications(CMSNode Node, User user, IAction Action) +30 umbraco.BusinessLogic.Actions.Action.RunActionHandlers(Document d, IAction action) +332 umbraco.content.PublishNode(List`1 Documents) +360 umbraco.dialogs.publish.Page_Load(Object sender, EventArgs e) +727 System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e) +15 System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e) +33 System.Web.UI.Control.OnLoad(EventArgs e) +99 umbraco.BasePages.BasePage.OnLoad(EventArgs e) +9 System.Web.UI.Control.LoadRecursive() +47 System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1436
Version Information: Microsoft .NET Framework Version:2.0.50727.1378; ASP.NET Version:2.0.50727.1378
is umbraco leaking connections????
|
Rank: Newbie
Joined: 6/6/2007 Posts: 9
|
Weird, maybe check out sql activity monitor see how many connections its opening? That error looks like the sql reader is not being closed. But looking at the function that is calling it, its closing the connection correctly so uh yea :hmm: need a bit more info. Do you have any custom action handlers?
|
Rank: Enthusiast
Joined: 8/17/2007 Posts: 12
|
no custom handlers. I have just published using umbraco page. did a left click and click on published. last time i checked the number of connections was about 100 or something like that. was not a normal number. I think isn't not closing all connection. but if you know where he opens the connection in the code try do something like this, every time he open write to a file, and every time he closes write again. if you what me to test you have to tell me where to look.
|
Rank: Newbie
Joined: 6/30/2008 Posts: 4
|
I was having this problem with a large amount of children to publish. I made sure that on the sql server that the number of connections was at 0 (unlimited) in the configuration properties. Then, I changed the max number of connections in the web.config file to a large amount (just added "Max Pool Size=1000;Min Pool Size=5;". This seemed to solve my problem.
|