You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/10/16 12:43:02 UTC
[jira] [Commented] (CXF-7878) ClientPolicyCalculator ignores
ConnectionRequestTimeout property
[ https://issues.apache.org/jira/browse/CXF-7878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16651615#comment-16651615 ]
ASF GitHub Bot commented on CXF-7878:
-------------------------------------
gyoetam opened a new pull request #460: CXF-7878: ClientPolicyCalculator ignores ConnectionRequestTimeout property
URL: https://github.com/apache/cxf/pull/460
https://issues.apache.org/jira/browse/CXF-7878
Timeout values set to random numbers in the test to avoid accidentally setting them to the same value as a default and not noticing.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
> ClientPolicyCalculator ignores ConnectionRequestTimeout property
> ----------------------------------------------------------------
>
> Key: CXF-7878
> URL: https://issues.apache.org/jira/browse/CXF-7878
> Project: CXF
> Issue Type: Bug
> Components: Transports
> Affects Versions: 3.2.6
> Reporter: Györgyey Tamás
> Priority: Major
> Labels: pull-request-available
>
> ClientPolicyCalculator#intersect() drops the value set with setConnectionRequestTimeout() from the returned policy. As a result, AsyncHttpConduit always uses the default value even if it is explicitly set by the user through a HTTPClientPolicy.
> A pull request with the fix will be provided on GitHub.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)