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.
On Fri, Jun 16, 2017 at 5:16 PM, Olaf Kock <tom...@olafkock.de> wrote: > If you don't have 4000 concurrent connections coming in to your > application server, this sounds suspiciously like your code gets a > connection from the pool and never returns it. Naturally, once the > connection has been used, it will turn idle (as no more statements are > executed), but if the connection pool does not know that nobody is > working on it any more, it won't hand the existing connection out to > anybody else. > > Inspect your code if you ever call connection.close(), which should > return the connection to the pool. > > Olaf > > > Am 16.06.2017 um 12:40 schrieb Sai Kumar: > > We are using 4000 connections for the particular DB in connection > > pool.Somehow,those 4000 connections are utilised in our production > > environment.If any new request is coming ,it is unable to fetch a > > connection because all the connections are utilised.But ,The actual > problem > > is after processing the request the connection pool will leave the > existing > > connection and ready for a new request to process.This is not happening > > here.All 4000 connections are never released. > > > > After processing ,all Active connections are moved to idle state ,but the > > idle connections are not re connecting to any other request later. > > > > Please help us on this ASAP. > > > > On Fri, Jun 16, 2017 at 3:49 PM, Olaf Kock <tom...@olafkock.de> wrote: > > > >> Sai Kumar, > >> > >> > >> Am 16.06.2017 um 12:06 schrieb Sai Kumar: > >>> Hi , > >>> > >>> We are using following tomcat version > >>> Apache Tomcat/7.0.52 > >>> Server number: 7.0.52.0 > >>> and currently we are facing a problem with this one. > >> While you give some description of things that happen in your > >> environment, it would help to reproduce them in a minimal system, e.g. > >> to provide a test case that demonstrates the issue in the simplest > >> possible way. > >> So far, your description gives little clue if your own webapp is > >> exhausting the connections itself, e.g. forgetting to return connections > >> to the pool. Ideally this would be a little code that exposes the > >> problem, together with steps to reproduce. > >> > >>> 1.Is there any Connection pool issue in the 7.0.52 version? > >>> 2.And it is fixed in 7.0.78 version? Or else tell me in which version > MY > >>> CASE issue is fixed. > >> I doubt that anyone would take on the "any" in question 1 - unless > >> somebody is actively aware of an actual bug in that version. > >> Question 2 would easily be answered with the minimal reproduction case > >> that I've talked about above. > >> > >> Olaf > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > >> For additional commands, e-mail: users-h...@tomcat.apache.org > >> > >> > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > > -- S Saikumar
