Hi Dan,
Thanks for the reply. It could possibly be the reason you have mentioned.
We will set the mentioned pool properties in our environment. I was only
trying to understand the pattern of this occurrence when I mentioned about
sharing the pooled connection. We have followed a similar discipline
On Nov 12, 2013, at 4:39 AM, Isuruwan Herath wrote:
> Hi Devs,
>
> We are using tomcat jdbc-pool v7.0.28. In one of the development
> environments we have been intermittently getting an exception from above
> interceptor.
>
> ---
>
> Caused by: java.sql.
Hi Devs,
We are using tomcat jdbc-pool v7.0.28. In one of the development
environments we have been intermittently getting an exception from above
interceptor.
---
Caused by: java.sql.SQLException: PooledConnection has already been closed.
at
org.apach
