hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kalam Shaik (JIRA)" <j...@apache.org>
Subject [jira] Created: (HTTPCLIENT-912) we are seeing more than 20,000 java threads in waiting state in java thread dump and after a while the tomcat crashes
Date Mon, 15 Feb 2010 04:07:28 GMT
we are seeing more than 20,000 java threads in waiting state in java thread dump and after
a while the tomcat crashes
---------------------------------------------------------------------------------------------------------------------

                 Key: HTTPCLIENT-912
                 URL: https://issues.apache.org/jira/browse/HTTPCLIENT-912
             Project: HttpComponents HttpClient
          Issue Type: Bug
          Components: HttpConn
    Affects Versions: 3.1 Final
         Environment: we are using jdk1.6.0_16 and tomcat 6.0.20 and we are linux  and this
is the os info
Linux qw-p-web20.qwplatform.com 2.6.18-92.el5 #1 SMP Tue Apr 29 13:16:15 EDT 2008 x86_64 x86_64
x86_64 GNU/Linux
            Reporter: Kalam Shaik
            Priority: Blocker


we are seeing more than 20,000 java threads in waiting state in java thread dump and after
a while the tomcat crashes and tomcat needs to restart to get it back to normal. Once it comes
back after few days it again crashes and needs restart. I am seeing the following thread in
threadump which is running state and all others are in waiting state.

TP-Processor25" daemon prio=10 tid=0x000000004473c000 nid=0x4da runnable [0x000000004f765000]
   java.lang.Thread.State: RUNNABLE
        at java.net.SocketInputStream.socketRead0(Native Method)
        at java.net.SocketInputStream.read(SocketInputStream.java:129)
        at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
        at java.io.BufferedInputStream.read(BufferedInputStream.java:237)
        - locked <0x00002aaab8b79c08> (a java.io.BufferedInputStream)
        at org.apache.commons.httpclient.HttpParser.readRawLine(HttpParser.java:78)
        at org.apache.commons.httpclient.HttpParser.readLine(HttpParser.java:106)
        at org.apache.commons.httpclient.HttpConnection.readLine(HttpConnection.java:1116)
        at org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionAdapter.readLine(MultiThreadedHttpConnectionManager.java:1413)
        at org.apache.commons.httpclient.HttpMethodBase.readStatusLine(HttpMethodBase.java:1973)
        at org.apache.commons.httpclient.HttpMethodBase.readResponse(HttpMethodBase.java:1735)
        at org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:1098)
        at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:398)
        at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171)
        at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397)
        at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:323)
        at com.fastsearch.esp.search.http.HttpSearchEngine.searchInternal(HttpSearchEngine.java:592)
        at com.fastsearch.esp.search.http.HttpSearchEngine.search(HttpSearchEngine.java:279)
        at com.fastsearch.esp.search.view.SearchView.search(SearchView.java:233)

I think the code from our side is doing right to release the connection,but some how this
seems to be not working accurately.

Could you please let us know is this bug already seen anywhere? Could you please recommend
any work around or upgrades.

Thanks for your help
Kalam

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org


Mime
View raw message