On Mon, 28 Nov 2011 10:13:23 +0100, bdm <[email protected]> wrote:
Hello, I have got a problem with a small crud app developed with tapestry. This is a low traffic application so it can be unused for more than one day before we need it again. The problem is we got a timeout with the jdbc connection and we need to restart the application container (Glassfish) to have the jdbc connection up again.
Sounds like you haven't configured a connection pool for Hibernate. The default pool implementation is not suitable for production. IIRC Hibernate even logs a warning about this. C3P0 is a popular connection pool, you can use that if you set this property hibernate.connection.provider_class = org.hibernate.connection.C3P0ConnectionProvider You can probably get more help on the Hibernate forum. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
