You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hc.apache.org by "Kalam Shaik (JIRA)" <ji...@apache.org> on 2010/02/15 05:07:28 UTC

[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

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


[jira] Reopened: (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

Posted by "Kalam Shaik (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HTTPCLIENT-912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kalam Shaik reopened HTTPCLIENT-912:
------------------------------------


Please find this one from the thread dump. here this thread is locked.


"MultiThreadedHttpConnectionManager cleanup" daemon prio=10 tid=0x00000000440c7800 nid=0x358f in Object.wait() [0x00000000430f4000]
   java.lang.Thread.State: WAITING (on object monitor)
        at java.lang.Object.wait(Native Method)
        - waiting on <0x00002aaab36106d0> (a java.lang.ref.ReferenceQueue$Lock)
        at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:118)
        - locked <0x00002aaab36106d0> (a java.lang.ref.ReferenceQueue$Lock)
        at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:134)
        at org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$ReferenceQueueThread.run(MultiThreadedHttpConnectionManager.java:1122)


> 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


[jira] Resolved: (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

Posted by "Oleg Kalnichevski (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HTTPCLIENT-912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Oleg Kalnichevski resolved HTTPCLIENT-912.
------------------------------------------

    Resolution: Invalid

Your application is leaking connections. Make sure you _always_ call HttpMethod#connectionRelease() form a finally clause.

HttpClient 3.1 is no longer supported. Consider upgrading to 4.0.

Oleg

> 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
>         Attachments: threaddump2.txt
>
>
> 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


[jira] Updated: (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

Posted by "Kalam Shaik (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HTTPCLIENT-912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kalam Shaik updated HTTPCLIENT-912:
-----------------------------------

    Attachment: threaddump2.txt

Please find the thread dump attached. Thanks for your time.
Kalam

> 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
>         Attachments: threaddump2.txt
>
>
> 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


[jira] Commented: (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

Posted by "Kalam Shaik (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HTTPCLIENT-912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12834296#action_12834296 ] 

Kalam Shaik commented on HTTPCLIENT-912:
----------------------------------------

Could you please let me know the steps to upgrade? Is it just replacing the new jar with the old jar? 

thanks,
Kalam

> 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
>         Attachments: threaddump2.txt
>
>
> 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


[jira] Resolved: (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

Posted by "Oleg Kalnichevski (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HTTPCLIENT-912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Oleg Kalnichevski resolved HTTPCLIENT-912.
------------------------------------------

    Resolution: Invalid

TP-Processor25" daemon prio=10 tid=0x000000004473c000 nid=0x4da runnable [0x000000004f765000]
   java.lang.Thread.State: RUNNABLE
        at java.net.SocketInputStream.socketRead0(Native Method) 

The tread is blocked in the native socketRead0 method. That means the server is not sending data. 

This problem has nothing to do with HttpClient

Oleg

> 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


[jira] Commented: (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

Posted by "Sebb (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HTTPCLIENT-912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12834298#action_12834298 ] 

Sebb commented on HTTPCLIENT-912:
---------------------------------

That is a question for the HttpClient user list.

JIRA is not a support forum.

> 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
>         Attachments: threaddump2.txt
>
>
> 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