[
https://issues.apache.org/jira/browse/HTTPCORE-782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17981829#comment-17981829
]
Oleg Kalnichevski commented on HTTPCORE-782:
--------------------------------------------
> "TLS decrypt; status = OK; handshake = NEED_TASK; bytesConsumed = 0;
> bytesProduced = 0; end of stream = false"
[~Jason Mathison] Curious. At the very least it fully explains the event loop
in the TLS layer. I will look into it.
> Would there be any use /way to try to trace out the delegated tasks that
> "NEED_TASK" implies are being waited on?
Yes, there would. It would be very helpful to know what kind of potentially
blocking task the TLS session requires.
Oleg
> 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: Major
> Fix For: 5.3.5, 5.4-alpha1
>
> 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
