[
https://issues.apache.org/jira/browse/CXF-6913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Torsten Mielke closed CXF-6913.
-------------------------------
Thanks for the quick fix Freeman.
For the records Freeman added the text
{quote}
And if TLSClientParameters sets an SSLSocketFactory, as SocketFactory class
and SocketFactory#createSocket methods in particular are inherently blocking
and sockets instantiated in such a way cannot be used for asynchronous, so this
lead to use the HttpURLConnection based transport.
{quote}
to page
http://cxf.apache.org/docs/asynchronous-client-http-transport.html
> [doc] Setting SSLSocketFactory on TLSClientParameters switches from async to
> sync HTTP
> --------------------------------------------------------------------------------------
>
> Key: CXF-6913
> URL: https://issues.apache.org/jira/browse/CXF-6913
> Project: CXF
> Issue Type: Improvement
> Components: Documentation
> Affects Versions: 3.1.6
> Reporter: Torsten Mielke
> Assignee: Freeman Fang
> Labels: documentation
>
> The fix for CXF-5071 introduced a check in AsyncHTTPConduit.setupConnection()
> {code:java}
> if (uri.getScheme().equals("https")
> && clientParameters != null
> && clientParameters.getSSLSocketFactory() != null) {
> //if they configured in an SSLSocketFactory, we cannot do anything
> //with it as the NIO based transport cannot use socket created
> from
> //the SSLSocketFactory.
> o = false;
> }
> {code}
> that makes CXF switch from an asynchronous to a synchronous HTTP transport if
> the TLSClientParameters used sets an SSLSocketFactory.
> This behaviour is undocumented and has caused confusion among customers. Can
> we get this please documented on page
> http://cxf.apache.org/docs/asynchronous-client-http-transport.html
> Thanks,
> Torsten
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
