This shouldn't be a problem. The SQL connection pool is pretty robust. On Wed, Dec 17, 2008 at 3:21 AM, Thomas Koch <[email protected]> wrote:
> > Hi there - just noticed this little entry > http://www.hibernate.org/117.html#A15 > in the Hibernate "Advanced Problems". > > > Problem: > When I leave Hibernate running overnight, I come back and find that it > can no longer connect to the database. > > Answer: > (This is particularly common in the case of MySQL, wich times out JDBC > connections after a short time.) > You should never use Hibernate's built-in connection pooling in > production; it is non-scalable and non-fault-tolerant. Instead, use > DBCP or C3P0 (or, even better, an application server datasource). > > > Can anyone tell me if this is an issue with the NHibernate standard > configuration? I am personally using NHibernate 2.0 out of the box > with SQL Server 2005 in production, and have thus far not experienced > any problem with connectivity. > > Cheers, > Thomas > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
