On Tue, Jan 16, 2024 at 9:07 AM Christopher Schultz < ch...@christopherschultz.net> wrote:
> Hello, > > On 1/11/24 11:08, அருள்ராஜன் அ லை wrote: > > Hi > > > > We are using Tomcat 9.0.84 and Tomcat DBCP2 connection pool and the DB is > > Oracle 19c. We are seeing the closed connections and the standment > objects > > are not cleared even after the connection says closed. Anybody faced > > similar issue ? > > > > Here is the values in tomcat context.xml > > > > maxWaitMillis="60000" > > maxIdle="10" > > logAbandoned="true" > > removeAbandonedOnBorrow="true" > > removeAbandonedOnMaintenance="true" > > removeAbandonedTimeout="60" > > removeAbandoned="true" > > testonBorrow="true" > > testWhileIdle="true" > > timeBetweenEvictionRunsMillis="120000" > > driverClassName="oracle.jdbc.OracleDriver" > > accessToUnderlyingConnectionAllowed="true" > > maxTotal="200" > > type="javax.sql.DataSource" > > > > How are you observing the "closed connections" and the "not-closed > statements"? > > Are you using the latest Oracle driver that is available for your platform? > One more question: Why do you have accessToUnderlyingConnectionAllowed set to true? Is the application code possibly using this to access physical connections directly (and maybe closing them)? You can grep the code for getInnermostDelegate() to check for this. Phil > > -chris > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
