Bug 68295 - Connection has already been closed - Tomcat connection pool
Summary: Connection has already been closed - Tomcat connection pool
Status: NEW
Alias: None
Product: Tomcat Modules
Classification: Unclassified
Component: jdbc-pool (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal (vote)
Target Milestone: ---
Assignee: Tomcat Developers Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-12-05 18:08 UTC by Angadpaul
Modified: 2023-12-13 18:26 UTC (History)
0 users



Attachments
Logs from batch job (23.49 KB, text/plain)
2023-12-05 18:08 UTC, Angadpaul
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Angadpaul 2023-12-05 18:08:49 UTC
Created attachment 39435 [details]
Logs from batch job

As per the documentation on https://tomcat.apache.org/tomcat-7.0-doc/jdbc-pool.html. We have implemented Tomcat Connection pool in our project. It is a Java batch job and we are using below properties.

maxTotal="100"
maxIdle="20" 

removeAbandoned="true"
removeAbandonedTimeout="1800"

Our batch job abruptly ends with below logs:
exitDescription=org.springframework.transaction.TransactionSystemException: Could not roll back JPA transaction; nested exception is org.hibernate.TransactionException: Unable to rollback against JDBC Connection\n\tat org.springframework.orm.jpa.JpaTransactionManager.doRollback

I need to understand what should be the combination of these params? removeAbandoned as per documentation is for longest running query but this fails even the queries run less than 5 mins. 
Is there a different param like maxAge we need to use?
Also attcahed complete logs too.
Pls help as this is impacting our batch jobs.

Thanks
Angadpaul