[
https://issues.apache.org/jira/browse/CXF-4765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14152955#comment-14152955
]
Maciek Kurek commented on CXF-4765:
-----------------------------------
Change need to be verified.
There is nothing changed in ClientPolicyCalculator and neither in HTTPConduit
since version 2.7.2.
Checked sources : apache-cxf-2.7.3-src.zip apache-cxf-2.7.12-src.zip
apache-cxf-3.0.1-src.zip
available at http://cxf.apache.org/download.html.
> can't set timeout in message HTTPClientPolicy if it is not set in conduit
> -------------------------------------------------------------------------
>
> Key: CXF-4765
> URL: https://issues.apache.org/jira/browse/CXF-4765
> Project: CXF
> Issue Type: Bug
> Components: Transports
> Reporter: Vadim Beilin
> Assignee: Daniel Kulp
> Fix For: 2.6.6, 2.7.3
>
>
> This code in ClientPolicyCalculator.intersect (previously in
> PolicyUtils.intersect) tries to combine timeout values from two policies by
> taking the smaller:
> {code}
> if (p1.isSetConnectionTimeout() || p2.isSetConnectionTimeout()) {
> p.setConnectionTimeout(Math.min(p1.getConnectionTimeout(),
> p2.getConnectionTimeout()));
> }
> if (p1.isSetReceiveTimeout() || p2.isSetReceiveTimeout()) {
> p.setReceiveTimeout(Math.min(p1.getReceiveTimeout(),
> p2.getReceiveTimeout()));
> }
> {code}
> Together with HTTPClientPolicy returning hardcoded default timeouts when not
> set (30000 ms for connect, 60000 for receive), it means that one cannot, eg,
> set receiveTimeout in a message policy to 2 min, if the timeout is left unset
> in the conduit.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
