Hello dear Jetspeed users!

We're using Jetspeed with PostgreSQL and had to learn that using the default
connection pooling leaves database connections open. So after a while the
database refuses any further connections which leads to an ugly 'horrible
exception' screen.

We found out that this problem is known by other users and there was a hint
to use JNDI connection pooling which seems to manage connections in a
smarter way.
Unfamiliar with JNDI we found ourself in deep trouble to get our application
run.

We already have found some examples how to configure tomcat's server.xml and
web.xml, but we are wondering how to make it run with the Jetspeed
application.

Could anybody show us an example how the torque.properties has to be
configured for JNDI use?
Do we have to change any parts of our implementation when using JNDI
connection pooling?
Does anyone know another solution that helps solving the connection problem?

Any hint helps, thank you!

Regards,
Harry





Reply via email to