[CXF-4765] can't set timeout in message HTTPClientPolicy if it is not set in conduit

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.6.6, 2.7.3
• Component/s: Transports
• Estimated Complexity: Unknown
• Assignee: Daniel Kulp
• Reporter: Vadim Beilin
• Created: 18/Jan/13 14:10
• Updated: 30/Sep/14 08:33
• Resolved: 24/Jan/13 17:27

Description

This code in ClientPolicyCalculator.intersect (previously in PolicyUtils.intersect) tries to combine timeout values from two policies by taking the smaller:

        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()));
        }

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.