[
https://issues.apache.org/jira/browse/HTTPCORE-782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17952377#comment-17952377
]
Oleg Kalnichevski commented on HTTPCORE-782:
--------------------------------------------
> That seemed like a reasonable stack location to me. What is your
> interpretation?
[~Jason Mathison] You are right. It looks plausible.
Please apply this patch to your local copy of HttpCore [1] or build it from my
private branch [2], deploy, run, collect the logs, and attach them to this
issue.
Oleg
[1]
https://github.com/ok2c/httpcomponents-core/commit/7ffa29ac0de931e638f6d462aff43e91ca5a068e
[2] https://github.com/ok2c/httpcomponents-core/tree/HTTPCORE-782
> Occasional thread stuck in
> org.apache.hc.core5.reactor.ssl.SSLIOSession.decryptData
> -----------------------------------------------------------------------------------
>
> Key: HTTPCORE-782
> URL: https://issues.apache.org/jira/browse/HTTPCORE-782
> Project: HttpComponents HttpCore
> Issue Type: Bug
> Components: HttpCore
> Affects Versions: 5.3.4
> Reporter: Jason Mathison
> Priority: Blocker
> Attachments: Thread Stack Traces
>
>
> We have a service that is occasionally having a thread get stuck in a state
> where it consumes as much CPU as possible. The thread will create and release
> a huge number of objects without causing an overall memory leak.
> We gathered a series of stack traces from this happening on one of our
> production instances that indicates that the thread is stuck inside of the
> "while (inEncryptedBuf.hasRemaining()) { " in
> org.apache.hc.core5.reactor.ssl.SSLIOSession.decryptData(SSLIOSession.java)
> This issue has been happening a couple of times a week for several weeks. We
> believe that it is always happening against a specific endpoint and are
> attempting to gather more information about what this endpoint is doing.
> This issue started happening a few weeks ago when we were on a slightly older
> version of this library. We happened to update to the latest version of these
> libraries and this is continuing to happen. We have had no success in causing
> this issue to happen in our testing environments where we could gather a heap
> dump.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org
For additional commands, e-mail: dev-h...@hc.apache.org
