Uploaded image for project: 'CloverDX'
  1. CloverDX
  2. CLO-7695

WebServiceClient does not respect HTTP headers in properties

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: rel-4-1-0
    • Fix Version/s: rel-4-1-2
    • Component/s: Engine
    • Security Level: Users (General product issues)
    • QA Testing:
      UNDECIDED
    • OTRS_Ticket_ID:
      2015112010000074

      Description

      It seems that WSC opens multiple TCP connections when sending a request. And most of them ignore HTTP headers set in WSC component. I have done a stress test and this is the result:

      1) A graph containing 20 HTTPConnectors was started 60 times in two minutes. The number of TCP connections stuck in CLOSE_WAIT state was approximately 20700 at the peak. They were closed automatically a few minutes after the test was finished.
      2) The same as step 1 but with an additional HTTP header "connection=close". The number of TCP connections stuck in CLOSE_WAIT state was 0 for the whole time and did not increase at all. The header obviously helped.
      3) A graph containing 20 WebServiceClients was started 60 times in two minutes. The number of TCP connections stuck in CLOSE_WAIT state was approximately 133035 at the peak. They were closed automatically a few minutes after the test was finished.
      4) The same as step 3 but with an additional HTTP header "connection=close". The number of TCP connections stuck in CLOSE_WAIT state was approximately 127740 at the peak. They were closed automatically a few minutes after the test was finished. But the header seems to have very little impact on the result (if any, considering measurement errors).

      Investigate the behavior, please, and try to fix it. All TCP connections made from WSC should respect the settings.

        Attachments

          Activity

            People

            Assignee:
            hajdam Miroslav Hajda (Inactive)
            Reporter:
            imriskal Lubos Imriska
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 6 hours
                6h