Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...COnnection Pooling IssueCOnnection Pooling Issue
Previous
 
Next
New Post
10/11/2006 8:45 PM
 

I am getting connection pooling error when I am trying to access the DNN Site running on IIS. The backend database server is Sql Server 2005.

It was working fine till couple of hours ago and have stopped working after been left ideal for couple of hours. I am getting error-

*************************************

Unhandled Error

Error Details

File
Error   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.

*************************************

When this error occured, I checked the processes on Sql Server - Activity Monitor. It was fill by the database user which I use to connect from DNN site. I killed all the processes but still unable to get it work. Would appreciate if someone could update me-

  1. Why DNN connection pooling didn't work as I am using the same way to connect to database as other DNN modules?
  2. Why there was so many processes in database?
  3. Why is still now working?

Please advice

 

 

 
New Post
10/11/2006 10:28 PM
 

 

It sounds like a DataReader that has not been closed properly in the code.

Are you using any custom modules, or is this an "out of the box" installation?


DotNetNuke Modules from Snapsis.com
 
New Post
10/12/2006 7:11 PM
 

Hi John,

Thanks for quick reply.

Yes, I am using the custom Module. I only thing which I did is in all new module delete the DataProvider and SqldataProvider class and instead call "DotNetNuke.Data.DataProvider" class straight from controller class.

E.g-
return CBO.FillObject<LocationInfo>((IDataReader)DataProvider.Instance().ExecuteReader("Location_FindSingle", LocationInfo.LocationId));

Where DataProvider refere to "DotNetNuke.Data.DataProvider"

Do this class or "CBO" class of core DotNetNuke is handling the connection properly?

 

 
New Post
10/13/2006 8:20 AM
 


That's going to return an open DataReader.

Whatever method that calls that one and consumes the DataReader will need to make sure it closes it.


DotNetNuke Modules from Snapsis.com
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...COnnection Pooling IssueCOnnection Pooling Issue


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out