Hi all. Just recently upgraded an umbraco solution from v. 4.5.2 to v. 4.6.1 and experienced a Timeout exception when clicking on a node in the content tree that has a macrocontainer.
I created a fresh install (4.6.1) to test it, and created 22 test macros, and after clicking a node (with a macro container property) about15 times I get this exception:
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.
Macro Container bug in 4.6.1?
Hi all. Just recently upgraded an umbraco solution from v. 4.5.2 to v. 4.6.1 and experienced a Timeout exception when clicking on a node in the content tree that has a macrocontainer.
I created a fresh install (4.6.1) to test it, and created 22 test macros, and after clicking a node (with a macro container property) about15 times I get this exception:
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.
A similar bug is already reported here http://umbraco.codeplex.com/workitem/29874.
Difference is that I only set 4 Allowed Macros on my doctype.
Anybody experienced this too, or perhaps know of a fix?
Best regards Sune
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.