expend effort determining why the app isn't releasing the
> connections, as that's the real problem.
>
Done. We followed the JNDI datasource reccomendations on the Tomcat web page
and got bit. It was my fault for cutting and pasting so verbatim. The app
thanks for your help. I think I'll try changing resource names. A name that
includes the appName would help prevent collisions, especially on a shared
server, where I don't own all the apps.
John Gorkos
-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
On Wednesday 01 November 2006 11:58, Christopher Schultz wrote:
> John,
>
> John Gorkos wrote:
> > I use per-context JNDI handles to
> > the same Postgres database for multiple apps running inside tomcat. Each
> > context.xml sets up connection limits, max idle, et
not set up per-context pools, but rather share one
pool among all contexts, even though I specified pools per context? If it
only uses one pool, which set of configuration params does it choose (since I
set different params in each context.xml).
Thanks!
J
