Sai, May I suggest that you update your production system and see if that helps? No matter if the problem is in the tomcat version or your software, Tomcat 7.0.52 is over three years old, and contains many security related problems. From the release notes I see also quite a few performance and stability related changes, so you may quite easily see changed behavior. (Plus the Bugzilla you mentioned - solved in 2014 in r1613137)
As Olaf said, your request is a pretty difficult question to be answered, as each of us needs to have a full memory of all changes to the connection pool and see a correlation to your problem. It would certainly be helpful to answer his questions so at least Olaf is able to find a way to help you. From my experience, connection pool issues - if they appear all of a sudden with new application releases and new functionality - are related to application handling of the connections, timeouts and error handling (eg. connection closing in finally blocks). Kind regards Peter > Hi, > Please let anyone confirm me that,Is there is any issue regarding the > connection pool in Tomcat V7.0.52 or older versions. > And,In which version Connection pool Issue was resloved. > > Thank you > > On Mon, Jun 19, 2017 at 2:58 PM, Sai Kumar <saikumarsapar...@gmail.com> > wrote: > > > Hi , > > Need one help.I just seen this. > > *Bug 53367* <https://bz.apache.org/bugzilla/show_bug.cgi?id=53367> - > > Database > > failure may cause pool to hang - in bugzilla., > > My problem is something related to this case.And the fix included two > > files.. > > 1.FairBlockingQueue.java > > 2.Bug53367.java > > Can you please tell me .how to replace or deploy those files and test my > > case. > > I have no idea about it.So please tell me clearly. > > > > Thank you > > > > On Fri, Jun 16, 2017 at 5:39 PM, Olaf Kock <tom...@olafkock.de> wrote: > > > >> > >> 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 > >> > >> > > > > > > -- > > S Saikumar > > > > > > -- > S Saikumar > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
