Created attachment 35057 [details] Please find the attached screenshot for more details Hi Team, 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. We have an issue with connection pool. Actually we are using specific connections but some how all the connections are utilized. If any new request come then it is unable to fetch a connection because pool is empty. But in real case there is no chance of using that much of connections parallel So as per our analysis following are our observations. We are using max idle connections are 30 , but if we do the operations and calculate the connections using Jconsle then IDLE connections are more than 30. Please find attached screenshot for your reference. And Please let us know is there any solution for this issue. Thank you in advance. Thanks Dillesh
Comment on attachment 35057 [details] Please find the attached screenshot for more details Please update to latest 7.x and try test again. It might have been fixed since .52.
(In reply to mgrigorov from comment #1) > Comment on attachment 35057 [details] > Please find the attached screenshot for more details > > Please update to latest 7.x and try test again. It might have been fixed > since .52. Hi Team, Thank you for your quick response. So this issue is existed with 7.0.52 version. And please let us know what are the issues existed in 7.0.52 version. Thank you in advance. Thanks Dillesh
Please consult with the changelog to see what changes there are since .52. Please try 7.0.78! 7.0.52 cannot be fixed! Any fixes will go in 7.0.79+.
There is not enough information in this report to enable the problem to be replicated for investigation. As previously suggested, please test with the latest stable release and if you still experience problems please follow up on the users mailing list. If the mailing list discussion concludes that there is a Tomcat bug, feel free to re-open this issue. You'll need to provide the information that demonstrates that there is a bug. For example, a test case that demonstrates it, code analysis that shows there is a problem etc.
(In reply to Mark Thomas from comment #4) > There is not enough information in this report to enable the problem to be > replicated for investigation. > > As previously suggested, please test with the latest stable release and if > you still experience problems please follow up on the users mailing list. > > If the mailing list discussion concludes that there is a Tomcat bug, feel > free to re-open this issue. You'll need to provide the information that > demonstrates that there is a bug. For example, a test case that demonstrates > it, code analysis that shows there is a problem etc. Hi Team, Thank you for your quick response, And please confirm below points. Connection pool issue was in with 7.0.52 version? And it is fixed in 7.0.78 version? Please confirm above points so will test with tomcat 7.0.78 version. And will let you know the results. Thank you in advance. Thanks Dillesh
Please ask questions in users@ mailing list. BugZilla is not support forum!
(In reply to mgrigorov from comment #6) > Please ask questions in users@ mailing list. > BugZilla is not support forum! Hi Team, Thank you for your support. Thanks Dillesh