[ 
https://issues.apache.org/jira/browse/HTTPCORE-716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17558913#comment-17558913
 ] 

Oleg Kalnichevski commented on HTTPCORE-716:
--------------------------------------------

[~sanojpunchihewa] I came up with a better solution that should also fix 
HTTPCORE-717. Please review / test:

[https://github.com/apache/httpcomponents-core/commit/88ae6598f0b5903e12d00a394f18578aa83f0d68]

Oleg

> High CPU usage noticed for HTTPS GET requests with large payload
> ----------------------------------------------------------------
>
>                 Key: HTTPCORE-716
>                 URL: https://issues.apache.org/jira/browse/HTTPCORE-716
>             Project: HttpComponents HttpCore
>          Issue Type: Bug
>          Components: HttpCore NIO
>    Affects Versions: 4.4.14, 4.4.15
>            Reporter: Sanoj Punchihewa
>            Priority: Major
>         Attachments: HTTPCORE.postman_collection.json, HttpNIOTestServer.jar, 
> HttpNIOTestServer.zip, HttpNIOTestServer2.zip, testclient 2.zip, 
> testclient.jar
>
>
> We are using 4.4.14 of HttpCore NIO. We are having an issue while sending an 
> *HTTPS GET* request to the server with a large payload where the CPU usage 
> seems to increase and stays on forever. We debugged and found out that after 
> the HTTPS response is written back to the client, the server tries to close 
> the connection. We found out that the condition [1] which gets executed in 
> order to make the state closed becomes false forever and hence it keeps on 
> trying to close. It was observed that inPlain.hasData() is always true.
> We have attached a sample POSTMAN request and a server in order to reproduce 
> the issue.
> Appreciate your help on this issue.
> [1]-[https://github.com/apache/httpcomponents-core/blob/rel/v4.4.14/httpcore-nio/src/main/java/org/apache/http/nio/reactor/ssl/SSLIOSession.java#L388]
> Thanks,
> Sanoj



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to