In 6.0 we used to have an issue were our Connection Pool fills up occasionally. Looks like its happening again in 6.1.
ErrorType: Primary| ErrorCount: 3| App: NPD| SessionId: 7163a4b4-35bb-8916-63d7-db9b54d5b827| UserId: stewartmo| IsNewSession: False| ServerID: 10.31.11.21| Misc: |
Exception: System.Web.HttpException: Error executing child request for /npd/Activity/ActivityEditorPopup.aspx. ---> System.Web.HttpUnhandledException: Exception of type 'System.Web.HttpUnhandledException' was thrown. ---> Xeno.Data.ConnectionPoolEmptyException: No more connections can be created. They are all being used.
We can check it using : http://pdm2.tyson.com/npd/WebCommon/AdminForms/ConnectionPoolInfo.aspx
I suggest you file an SR with support, as we have not experienced this issue. In fact, I just double checked a few of our environments, and the connections are set to 8.
Please include as much information as you can, including:
- typical user click streams
- info on validations, guard conditions, custom code *
- if above exists, is it reproducible on a vanilla install with no customization?
- is this limited to the ActiviyEditorPopup.aspx page?
* Trey, if i recall, I thought this is where the problem lied in 6.0. a custom validation or guard condition was improperly firing off new connections.
I looked thru all the error event logs that got thrown yesterday when this started, and its mostly off Error executing child request for /npd/MainPage/NPD.aspx. & Error executing child request for /npd/Activity/ActivityEditorPopup.aspx
Does this have something to do with the fact that we have to deploy our custom DLLs to the npd/bin even though we have no validations or guards for NPD?
We have no NPD validators. We have other customizations that do not explicitly create any database connections. They access the data objects so any database connections are opened by framework. We also are placing GSM validation and guard condition assemblies in the npd/bin folder because the app expects them there even though they are not directly used.
The Validation framework loads up all validation factories, regardless of where they are used.
If none of your validation factories (not the validator classes, but the factories that create them) are loading up data, even if they aren't being used in NPD, then that should be fine. Log an SR with support like Matt suggested.