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.apache.tomcat.jdbc.pool.DisposableConnectionFacade.invoke(DisposableConnectionFacade.java:69)
at $Proxy14.prepareStatement(Unknown Source)
at
org.wso2.carbon.dataservices.core.description.query.SQLQuery.createProcessedPreparedStatement(SQLQuery.java:1367)
-------------------------------------------
We are not using a very high volume and we have not set pool properties to
values other than the defaults. It is really difficult to recreate this and
I have tried running the unit tests with different numbers to pool
configurations, but no success in reproducing above.
IIUC, this occurs when connection is shared in a multi-threaded scenario.
Possibly, one is trying to do some operation while other trying to close it
and return to the pool. Has there been any major concurrency related
improvements done after v7.0.28?
Really appreciate if you could give any sort of input on the cause of the
above.
Thanks and Regards!
Isuruwan
--
Isuruwan Herath
Technical Lead
Contact: +94 776 273 296
