Am 16.06.2017 um 14:00 schrieb Sai Kumar: > There is no problem with code,We are closing the connections properely. > This issue is occured in production side.We are highly suspecting that > there is an issue with the Tomcat server( V7.0.52). First of all,Please let > us know if there is any bug regarding the Connection pool in tomcat V7.0.52 > .If yes,tell me which version to be use to eradicate this issue. > Again we are confirming that ,there is no problem with the code.
This way we're back on my initial comment: "any bug regarding connection pool" is quite a broad question to ask. * How many /concurrent/ connections does your production server handle? * How many http handler (threads) did you configure on the machine that has the 4000 database connections? * How long are these connections leased from the pool on average / max? * Have you tried reproducing this in a minimal code environment? Olaf --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
