Uploaded image for project: 'Axis2'
  1. Axis2
  2. AXIS2-5100

AbstractHTTPSender.initializeTimeouts changes timeouts for shared HttpClient which is not thread safe

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Minor
    • Resolution: Fixed
    • None
    • 1.6.0
    • transports
    • None

    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.

      Attachments

        Activity

          People

            Unassigned Unassigned
            gowa Igor Kamyshnikov
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: