Velocity Reviews - Computer Hardware Reviews

Velocity Reviews > Newsgroups > Programming > ASP .Net > ASP .Net Web Services > Connection Pool Issue

Reply
Thread Tools

Connection Pool Issue

 
 
Kerry
Guest
Posts: n/a
 
      05-23-2008
Hello, I'm having a problem with connection pooling from my ASP.NET Web
Service. I have two identical servers (Software wise, hardware is different).
Server A and Server B both are running Windows 2000 Server sp4, Framework
2.0.50727 and 1.1.4322, IIS 5 and using the .Net SqlClient Data Provider.

When connecting via my .NET client app to the service on Server A the DB
connections to SQLServer 2005 sp2 re-uses the connections perfectly however
when connecting to ServerB which runs the exact same service connections are
being used up then I get the dreaded "The timeout period elapsed prior to
obtaining a connection from the pool. " I have compared both servers and
cannot find the difference...I'm thinking somewhere down the line I installed
something which enabled connection pooling to function correctly on
ServerA...ServerB is new server which will replace ServerA. I have checked
all the usual places for enabling connection pooling. With each DB read
operation the connections are being used up as if it thinks each read is
coming from a different user.

1. Both Machines do not have a registry entry for StartConnectionPool = 1 so
since it works on ServerA I assume ServerB does not need it , I created this
just in case with no luck so I removed it.

2. Connection string on both servers use Max Pool Size=10;Min Pool Size=1,
since this is Development 10 is sufficient and again ServerA runs fine with
this, i don't even need to specify connectionpool=true property.

3. Going to the ODBC Adminstrator, Connection Pooling is 'On' for the
Drivers SQLServer(200.85.112 and SQL Native Client(2005.90.3042) on both
Servers. Connections are set to remain in the pool for 60 seconds.

Is there something I could be missing or some utility that could turn on
connection pooling for the .Net SqlClient Data Provider...registry
entry,config file, IIS5 command line param.

Thanks

 
Reply With Quote
 
 
 
 
Kerry
Guest
Posts: n/a
 
      05-23-2008
I never thought that maybe ServerA never worked and ServerB is working as it
should since its a brand new setup. I just assumed that a low connection
count was an indication that it was working properly i.e re-using connections
that already existed. I increased the Max Pool size to 100...the problem has
dissappeared as I knew it would cause on production I set the the size to 100
also I notice the connection count fluculates between 8-15 connections which
also indicates that connections are being released/re-used etc....I'm
thinking now that my value of 10 maybe was too low and that was causing the
problem...even setting it to 20 shows no ill effects...I was so dead set on
getting it to work with 10.


Thanks for triggering a change of thought to this issue.

"Patrice" wrote:

> Max pool size 10 seems low... My personal preference is to avoid messing
> wiht default values unless I'm 100 % sure it's worth. What if you try the
> "perfmon.exe" to check pooling counters ?
>
> My first thought would be that connection poolling is actually disabled on A
> making this problem invisible while it is enabled on B showing the problem
> because of the low connection count ?
>
> Good luck. Seems hard to diagnose....
>
> --
> Patrice
>
>
> "Kerry" <(E-Mail Removed)> a crit dans le message de groupe
> de discussion : http://www.velocityreviews.com/forums/(E-Mail Removed)...
> > Hello, I'm having a problem with connection pooling from my ASP.NET Web
> > Service. I have two identical servers (Software wise, hardware is
> > different).
> > Server A and Server B both are running Windows 2000 Server sp4, Framework
> > 2.0.50727 and 1.1.4322, IIS 5 and using the .Net SqlClient Data Provider.
> >
> > When connecting via my .NET client app to the service on Server A the DB
> > connections to SQLServer 2005 sp2 re-uses the connections perfectly
> > however
> > when connecting to ServerB which runs the exact same service connections
> > are
> > being used up then I get the dreaded "The timeout period elapsed prior to
> > obtaining a connection from the pool. " I have compared both servers and
> > cannot find the difference...I'm thinking somewhere down the line I
> > installed
> > something which enabled connection pooling to function correctly on
> > ServerA...ServerB is new server which will replace ServerA. I have checked
> > all the usual places for enabling connection pooling. With each DB read
> > operation the connections are being used up as if it thinks each read is
> > coming from a different user.
> >
> > 1. Both Machines do not have a registry entry for StartConnectionPool = 1
> > so
> > since it works on ServerA I assume ServerB does not need it , I created
> > this
> > just in case with no luck so I removed it.
> >
> > 2. Connection string on both servers use Max Pool Size=10;Min Pool Size=1,
> > since this is Development 10 is sufficient and again ServerA runs fine
> > with
> > this, i don't even need to specify connectionpool=true property.
> >
> > 3. Going to the ODBC Adminstrator, Connection Pooling is 'On' for the
> > Drivers SQLServer(200.85.112 and SQL Native Client(2005.90.3042) on
> > both
> > Servers. Connections are set to remain in the pool for 60 seconds.
> >
> > Is there something I could be missing or some utility that could turn on
> > connection pooling for the .Net SqlClient Data Provider...registry
> > entry,config file, IIS5 command line param.
> >
> > Thanks
> >

>

 
Reply With Quote
 
 
 
Reply

Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Dynamic NAT pool doesn't report full when pool contains interface IP tom Cisco 0 10-09-2009 02:22 AM
does python have a generic object pool like commons-pool in Java Rick Lawson Python 8 07-16-2009 11:25 PM
PIX 501 issue routing between VPN pool and local pool eostrike Cisco 3 10-24-2008 09:43 PM
Connection Pool Issue Guadala Harry ASP .Net 2 06-11-2004 07:18 PM
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. Guoqi Zheng ASP .Net 4 06-03-2004 06:39 PM



Advertisments