Timeout expired - The timeout period elapsed prior to obtaining a connection from the pool. This may have occured because all pooled connections were in use and max pool size was reached.

Hi Friends,

We're encountering the above exception again and again. This is how we've used lightspeed in out application:

1. The connection string is stored in the web.config with Max Pool Size=1000; Min Pool Size=100 settings. The provider is System.Data.SqlClient.

2. Global asax's application start does the following: HttpContext.Current.Application["LSConnection"] = new LightSpeedContext("default");

3. A common class in defined with singleton pattern:

   public class DbContext { private static DbContext _instance;

   // Lock synchronization object
   private static object syncLock = new object();
   
   
   private LightSpeedContext<ClearLynxUnitOfWork> _context;
   
   
   protected DbContext()
   {
       _context = (LightSpeedContext<ClearLynxUnitOfWork>)HttpContext.Current.Application["LSConnection"];
       //_context = new LightSpeedContext<ClearLynxUnitOfWork>("default"); 
   }
   
   
   public static DbContext Instance
   {
       get
       {
           if (_instance == null)
           {
               lock (syncLock)
               {
                   _instance = new DbContext();
               }
           }
           return _instance;
       }
   }
   
   
   public LightSpeedContext<ClearLynxUnitOfWork> Context
   {
       get
       {
           return _context;
       }
   }
   

   }

But still we're facing the above issue. It would be great if someone could point us in the right direction.

How are you creating and disposing of your UnitOfWork instances? A UnitOfWork instance holds open its DB connection until it is disposed so this is the likely cause.

Jeremy