It sounds like you need to configure your connection pool to issue check statements before returning a connection (new or existing).
> -----Original Message----- > From: abangkis [mailto:abang...@gmail.com] > Sent: Saturday, January 10, 2009 17:42 > To: Tapestry users > Subject: Connection Problem > > Hello, > > I have an application that deployed with this kind of architecture : > > Apache httpd server -> Glassfishv2 -> Tapestry -> Tapestry-Hibernate -> > Mysql. > > And every 8 Hour or So, i've got a broken pipe error message. > > I've tried following this guide > http://www.codefin.net/2007/05/hibernate-and-mysql-connection- > timeouts.html, > but it didn't seems to work. Any other idea what kind of configuration > i should tweak in order for this not to happened ? > > the software versions are : > > Apache 2.2.8 > Sun Java System Application Server 9.1 (build b58g-fcs) > Tapestry 5.0.15 > Mysql 5.0.51a-3ubuntu5.4 > > Cheers , > > Abangkis > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org