Vadim Beilin created CXF-4765:
---------------------------------
Summary: 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
Priority: Minor
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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
