[
https://issues.apache.org/jira/browse/HTTPCLIENT-1522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14325952#comment-14325952
]
Oleg Kalnichevski commented on HTTPCLIENT-1522:
-----------------------------------------------
bq. So the code above is not correct, right?
I do not think so. In case of an I/O or an SSL protocol exception the
connection remains bound to a socket but the socket itself is closed by the
socket factory. So, the connection can be safely re-bound to another socket or
discarded.
bq. Is there any way to reset a ManagedHttpClientConnection instance?
{code:java}
ManagedHttpClientConnection conn = <...>;
final Socket socket = conn.getSocket();
if (socket != null) {
socket.close();
}
{code}
Oleg
> SNI support
> -----------
>
> Key: HTTPCLIENT-1522
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1522
> Project: HttpComponents HttpClient
> Issue Type: Bug
> Components: HttpClient
> Affects Versions: 4.3.4
> Reporter: Igor
>
> Running HttpRequest to https://touchpoint.tealeaveshealth.com/consume
> causes an error
> {code}
> javax.net.ssl.SSLProtocolException: handshake alert: unrecognized_name
> {code}
> to see how to fix, you can open
> *http://stackoverflow.com/questions/7615645/ssl-handshake-alert-unrecognized-name-error-since-upgrade-to-java-1-7-0*
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
