It seems that somehow your application is not properly disposing the connections... How do you handle sessions?
2010/10/5 Lakshman <[email protected]> > All, > > We have been using NHibernate 2.0.0 and Spring.NET 1.2 in our WCF web > services. > > We recently tried to migrate to NHibernate 2.1.2 and Spring.NET 1.3.0 > and since then started getting the following error at 20 TPS with 100 > users using Load Runner testing. > > “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” > > We mitigated that error by setting the Max Pool Size to 1000. But, the > web service server eventually crashed at 80 TPS with 400 users ( again > Load Runner). > > We thought we would move back to NHibernate 2.0.1. We didn't get any > errors or server crash with Spring.NET 1.3.0 and NHibernate 2.0.1 at > 80 TPS with 400 users ( again Load Runner). > > I am not sure what is going on with NH 2.1.2. Was it performance > tested at high loads? Did anyone else had similar issues? Is the fix > available in NH 3.0? > > Appreciate your inputs. > > Thanks, > Lakshman > > -- > You received this message because you are subscribed to the Google Groups > "nhusers" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<nhusers%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/nhusers?hl=en. > > -- You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/nhusers?hl=en.
