Ciao Fabio ww have a lot problem about this.. you mean just change like this in config file? <property name="transaction.factory_class">NHibernate.Transaction.AdoNetWithDistributedTransactionFactory</ property>
thanks On Dec 14, 12:30 pm, Fabio Maulo <[email protected]> wrote: > You don't have to go back to NH2.0.x > The NHibernate.Transaction.AdoNetWithDistributedTransactionFactory is there > even in NH3.0.0 > > > > > > On Mon, Dec 13, 2010 at 3:28 PM, Mauro <[email protected]> wrote: > > Hi Lakshman > > > after a week spent to find we got so many > > “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 reach the conclusion that what you report should be the problem. > > ..made some tests and we have same problem with around 25 tps .. but > > we cannot change the database from 2005 to 2008 right now and we > > cannot go back with the 2.0.1 version. > > > Can you suggest a quick fix ? > > please let me know.. > > thanks > > > On Nov 4, 1:37 pm, Lakshman <[email protected]> wrote: > > > We found the problem and applied a solution for this issue. > > > > This problem happens only with SQL Server 2005 as the backend and it > > > goes away with SQL Server 2008 R2. The root cause is the new class for > > > transaction management (the default under NH > > > 2.1.x)NHibernate.Transaction.AdoNetWithDistributedTransactionFactory. > > > > In NH 2.0.1 the transaction management class was > > > NHibernate.Transaction.AdoNetTransactionFactory which hasn't caused > > > any problem. > > > > Luckily, we were able to configure this as part of the NH > > > configuration. We configured the transaction.factory_class property > > > and had set it to NHibernate.Transaction.AdoNetTransactionFactory to > > > resolve the issue. > > > > On Oct 6, 12:44 pm, Jason Meckley <[email protected]> wrote: > > > > > how is spring handling session management. the problem isn't 2.1.2. > > > > the problem is how you are managing 2.1.2. > > > > > On Oct 6, 9:21 am, Lakshman <[email protected]> wrote: > > > > > > Thanks Jose. We delegate the session / transaction management to > > > > > Spring.NET. > > > > > > On Oct 5, 2:58 pm, José F. Romaniello <[email protected]> > > wrote: > > > > > > > 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]> > > <nhusers%[email protected]<nhusers%252bunsubscr...@googlegroups.com> > > > > > > > > > > . > > > > > > > For more options, visit this group at > > > > > > >http://groups.google.com/group/nhusers?hl=en.-Hidequotedtext- > > > > > > > - Show quoted text -- Hide quoted text - > > > > > - Show quoted text -- Hide quoted text - > > > > - Show quoted text - > > > -- > > 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. > > -- > Fabio Maulo- Hide quoted text - > > - Show quoted text - -- 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.
