You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Łukasz Nowak (Jira)" <ji...@apache.org> on 2020/04/28 10:11:00 UTC
[jira] [Updated] (CXF-8270) Persistent SSL connection is closed
when only URI path was changed
[ https://issues.apache.org/jira/browse/CXF-8270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Łukasz Nowak updated CXF-8270:
------------------------------
Description:
I am using Async HTTP transport ([https://cxf.apache.org/docs/asynchronous-client-http-transport.html]) in my client that is using JAXRSClientFactoryBean for proxy creation. I am observing two strange things:
* when invoking the same URI in the loop there is always leased one connection from the pool and the processing time is fine,
* when invoking two different REST methods that are available on the same server (e.g. [https://server.com/test1] and [https://server.com/test2] the AsyncHttpConduit is reseting sslState and this leads to connection close and creation of new one. The processing time is much higher as we need to process SSL handshake every time.
SSL state inside AsyncHTTPConduit should be reset only when host or port of the url was changed. The path of the URI could be changed and request should be reusingexisting SSL persistent connection.
was:
I am using Async HTTP transport ([https://cxf.apache.org/docs/asynchronous-client-http-transport.html]) in my client that is using JAXRSClientFactoryBean for proxy creation. I am observing two strange things:
* when invoking the same URI in the loop there is always is leased one connection from the pool and the processing time is fine,
* when invoking two different REST methods that are available on the same server (e.g. [https://server.com/test1] and [https://server.com/test2] the AsyncHttpConduit is reseting sslState and this leads to connection close and creation of new one. The processing time is much higher as we need to process SSL handshake every time.
SSL state inside AsyncHTTPConduit should be reset only when host or port of the url was changed. The path of the URI could be changed and request should be reusingexisting SSL persistent connection.
> Persistent SSL connection is closed when only URI path was changed
> ------------------------------------------------------------------
>
> Key: CXF-8270
> URL: https://issues.apache.org/jira/browse/CXF-8270
> Project: CXF
> Issue Type: Bug
> Components: Transports
> Affects Versions: 3.3.6
> Reporter: Łukasz Nowak
> Assignee: Colm O hEigeartaigh
> Priority: Major
>
> I am using Async HTTP transport ([https://cxf.apache.org/docs/asynchronous-client-http-transport.html]) in my client that is using JAXRSClientFactoryBean for proxy creation. I am observing two strange things:
> * when invoking the same URI in the loop there is always leased one connection from the pool and the processing time is fine,
> * when invoking two different REST methods that are available on the same server (e.g. [https://server.com/test1] and [https://server.com/test2] the AsyncHttpConduit is reseting sslState and this leads to connection close and creation of new one. The processing time is much higher as we need to process SSL handshake every time.
> SSL state inside AsyncHTTPConduit should be reset only when host or port of the url was changed. The path of the URI could be changed and request should be reusingexisting SSL persistent connection.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)