Wrox Programmer Forums
Go Back   Wrox Programmer Forums > SQL Server > SQL Server 2000 > SQL Server 2000
|
SQL Server 2000 General discussion of Microsoft SQL Server -- for topics that don't fit in one of the more specific SQL Server forums. version 2000 only. There's a new forum for SQL Server 2005.
Welcome to the p2p.wrox.com Forums.

You are currently viewing the SQL Server 2000 section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
 
Old May 23rd, 2006, 12:39 AM
Friend of Wrox
 
Join Date: Dec 2004
Posts: 221
Thanks: 0
Thanked 0 Times in 0 Posts
Default Connection pooling and Timeout

Hello All

having a problem in sign-in page, where i am using the best
of the sql server and recommanded connection string for sql 2000
(default) in vs.net 2003 1.1 as framework

here is the message...
========================================
Timeout expired. The timeout period
elapsed prior to obtain a connection
from the pool. This may have occurred
because all pooled connection were
in use and max pool size was reached.
========================================

when i click on signin button, i have created a dll which is has
a DBConnection class which is called to connect to the SQL
there i am using SP which takes 2 params UN and PWD.
conn string is written in web.config of the app.

I using the basic conn string like server, User Id, Inital Catalog and pwd. just these 4 properties. when i got this error only 4 person
were logging in at the same time.

so, let me know how to fix this ang get over ride of this problem.
hope to see your response as soon.

With Regards,
Raghavendra Mudugal
__________________
With Regards,
Raghavendra Mudugal
 
Old May 23rd, 2006, 10:04 AM
Friend of Wrox
 
Join Date: Jul 2003
Posts: 599
Thanks: 6
Thanked 3 Times in 3 Posts
Default

Hi,

I was getting the same error message. My particular problem was created because I was not closing a connection in a repeater. Closing the connection resolved the problem immediately. You can actually view the open connections while running the sign-in page by typing the following code into Query Analyzer:

EXEC sp_who

Hope this helps.

 
Old May 24th, 2006, 01:42 AM
Friend of Wrox
 
Join Date: Dec 2004
Posts: 221
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Hello,

Closing the connection, this is my first step I am doing after DB work is finished. As we all now OPEN connection as lately as possible and CLOSE connection as early as it can be. This is taken care by me in the early
stage itsself.

Well, I have know idea how to get rid of this. If you have any alternate.
Let me know

And, Thank you for replying me back.


With Regards,
Raghavendra Mudugal





Similar Threads
Thread Thread Starter Forum Replies Last Post
Connection Pooling problem. nitinp ASP.NET 2.0 Professional 2 July 9th, 2007 02:12 AM
Connection Pooling nigam.anand Apache Tomcat 0 October 18th, 2006 08:39 AM
connection pooling error aravwind ADO.NET 0 November 23rd, 2005 07:20 AM
Connection pooling in VB vijayma VB How-To 0 March 18th, 2005 03:51 AM
Connection Pooling with Beans angrycat Apache Tomcat 4 September 16th, 2004 06:11 PM





Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright (c) 2020 John Wiley & Sons, Inc.