Seems like you have a class called SearchClientRemoteClient which uses HTTPClient. Many threads seems to wait for remote responses. I guess you don't set any timeouts for the HTTPClient and therefore many threads hang in HttpClient.executeMethod() forever. You should ALWAYS set timeouts when using HTTPClient. :)
I hope this helps :) Christian 2013/5/17 Sascha Troll <sascha.tr...@geberit.com> > Hi ! > > I have problem with our Tomcat 7.0.40 (upgrade already done from 7.0.39 > and 7.0.37 and still the same issue). > > Its still running, but not longer accepting any connection on port 8080. > > Attached are the thread dumps which were created this morning when the > server was not longer available. > I cannot find any deadlocks and need some help to find the cause. > > > > Thanks > Sascha > > > > -------------------------------------------------------------------------------------------------- > Disclaimer: > The content of this e-mail (including attachments) is confidential and > intended for the use of the addressee only. If you are not the intended > recipient please delete the e-mail; dissemination or disclosure of its > content to anyone is strictly prohibited! > Before opening an attachment please check it for viruses. We accept no > liability for any damage caused by viruses. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > -- Christian Kaltepoth Blog: http://blog.kaltepoth.de/ Twitter: http://twitter.com/chkal GitHub: https://github.com/chkal
