Connection pooling with AJAX calls
Our web application is making multiple asynchronous AJAX calls to the database, we are making 5 calls at one time. These stored procedures take on average .25 seconds to execute. We are using connection pooling and opening 5 connections using the connection string. The problem that I am seeing is that even though these are 5 asynchronous connections, they all get funneled into 1 active connection in the pool and then it appears that everything gets queued up in the database. These 5 calls are taking an average time of 3 seconds to execute them all.
I am puzzled why they would not get executed at the same time and take advantage of the connection pool. I did find that if I opened another IE window with a separate sessionid, then those requests will go through one of the open connections in the pool.
Is there any way to force the requests to use any available connection regardless of the session ID? This is a .NET 3.5 web application running on IIS 6. Below is the connection string we are using.
Data Source=database;User Id=userID;Password=password;Pooling=true;Connection Lifetime=0;Connection Timeout=5;Decr Pool Size=1;Enlist=false;Incr Pool Size=5;Max Pool Size=50;Min Pool Size=5;Statement Cache Size=20
Any suggestions or information would be greatly appreciated!
Thanks!