[AXIS2-5100] AbstractHTTPSender.initializeTimeouts changes timeouts for shared HttpClient which is not thread safe

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 1.6.0
• Component/s: transports
• Assignee: Unassigned
• Reporter: Igor Kamyshnikov
• Created: 26/Jul/11 08:06
• Updated: 26/Jul/11 08:47
• Resolved: 26/Jul/11 08:47

Description

I have tried to set default timeouts for shared HttpClient in shared ConfigurationContext but it appears it is not possible to make it work because each call of AxisEngine.send(msgContext) (e.g. from OutInAxisOperation) overrides timeouts of HttpClient from MessageContext (where this timeout might not be even defined causing to use default 30 seconds timeout).

More over it appears it a threading issue because HttpClient could be shared by a number of threads. That's why I don't understand why configuration of HttpClient is changed by each call of AxisEngine.send.

This makes me not to use shared ConfigurationContext with shared HttpClient with MultithreadedHttpConnectionManager. It is required to create ConfigurationContext (and HttpClient, and HttpConnectionManager) for each stub instance.