-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160
Hi Peter,
it must be the underlying JDBC connection. I use an non-JTA datasource in an
5.5.17 TomCat together with an MySQl 5.0.24 database. As far as I know TomCat
doesn't support JTA. For performance reasons I'm storing entitymanager as static
variable to be used by several server connections simultaneously. Maybe that's
the reason for this? Unfortunately this error isn't easy to reproduce since it
occurred only after a while of waiting for hours without action. Reloading the
connecting pages twice has been the best solution for now. Connection got
reconnected after that. Since Glassfish has an reconnection feature for his pool
I was thinking about a similar feature for the non-JTA variant.
Thanks for help
Benjamin
Peter Krogh wrote:
> Benjamin,
>
> The TopLink connection pool doesn't timeout. What is the error that you are getting? Is it that the underlying JDBC connections are timing out, or that TomCat is timing out the connections?
>
> How are you configuring this exactly? Are you using a Non JTA datasource?
>
> -------- Original Message --------
> Subject: connection timeout
> Date: Thu, 24 Aug 2006 17:24:30 +0200
> From: Benjamin Graf <Benjamin.Graf_at_gmx.net>
> Reply-To: persistence_at_glassfish.dev.java.net
> To: persistence_at_glassfish.dev.java.net
>
> Hi everybody,
>
> I have a problem with the toplink connection pool. I use it in an tomcat 5.5 web
> application as database persistence api. But after a while (must be several
> hours) the connection is lost and an error occurred. Does anybody now a solution
> for avoiding pool timeouts or to get auto reconnect without error throwing?
>
> THX Benjamin
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (MingW32)
iD8DBQFE9bVN+oSgMM7Y9KsRAxkjAJ4zhTxpyjqfB8XZuEjhjoGw4cpXywCg6RVc
kEgYN1x8vJ0F8Zg5TZeYEfM=
=zokw
-----END PGP SIGNATURE-----