Uploaded image for project: 'OpenAM'
  1. OpenAM
  2. OPENAM-10897

Memory Leak in SAML perf test case

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: 14.0.0
    • Fix Version/s: 14.0.0
    • Component/s: performance, SAML
    • Labels:

      Description

      Since OpenAM 14.0.0-SNAPSHOT Build eaa230d59a (2017-March-15 10:39) we are seeing a memory leak on SAML perf test case which after a while starts throwing error on login.

      It can be recreated via pyforge test case : nohup python -u run-pybot.py -c perf -s saml OpenAM &
      using max heap as 5G and min 2G on local

      20170315 14:50:18.318 - WARN - ---- Errors --------------------------------------------------------------------
      > status.find.is(200), but actually found 401                         1 (100.0%)
      ================================================================================
      20170315 14:50:18.319 - WARN - Request:
      RestLogin: KO status.find.is(200), but actually found 401
      =========================
      Session:
      Session(SAML Flow,6,Map(timestamp.try -> 1489585723142, try -> 0, 31a5855d-3da6-4b5d-bacb-8b73c773fbd7 -> 21231, gatling.http.cache.dns -> io.gatling.http.resolver.ShuffleJdkNameResolver@3e5792cf, username -> user.28323, tokenid -> AQIC5wM2LY4Sfcx980wT46C6M5tMi5GuVBBMd5XPqr-OQyo.*AAJTSQACMDEAAlNLABQtNjA4NDU4MTA5NTM3MDU4NjE3NQACUzEAAA..*, timestamp.31a5855d-3da6-4b5d-bacb-8b73c773fbd7 -> 1489584902262, gatling.http.referer -> http://fourme.internal.forgerock.com:8082/fedlet/index.jsp, gatling.http.cookies -> CookieJar(Map(CookieKey(amlbcookie,internal.forgerock.com,/) -> StoredCookie(amlbcookie=01; domain=internal.forgerock.com; path=/,false,false,1489585734794))), password -> password),1489584902262,14604,OK,List(TryMaxBlock(try,io.gatling.core.action.InnerTryMax@1860c82d,KO), ExitAsapLoopBlock(31a5855d-3da6-4b5d-bacb-8b73c773fbd7,io.gatling.core.session.package$RichExpression$$$Lambda$158/935160003@4f4db240,io.gatling.core.action.InnerLoop@55051269)),io.gatling.core.protocol.ProtocolComponentsRegistry$$Lambda$217/1663738275@57c623ec)
      =========================
      HTTP request:
      POST http://fourme.internal.forgerock.com:8080/openam/json/authenticate?realm=
      headers=
      Accept: application/json
      X-OpenAM-Username: user.28323
      Content-Type: application/json
      Accept-API-Version: protocol=1.0,resource=1.0
      User-Agent: curl/7.43.0
      X-OpenAM-Password: password
      Referer: http://fourme.internal.forgerock.com:8082/fedlet/index.jsp
      Content-Length: 2
      Host: fourme.internal.forgerock.com:8080
      stringData={}
      =========================
      HTTP response:
      status=
      401 Unauthorized
      headers= 
      Server: Apache-Coyote/1.1
      X-Frame-Options: SAMEORIGIN
      Set-Cookie: amlbcookie=01; Domain=internal.forgerock.com; Path=/
      Cache-Control: no-cache, no-store, must-revalidate
      Content-API-Version: resource=1.2
      Expires: 0
      Pragma: no-cache
      Content-Type: application/json;charset=UTF-8
      Content-Length: 40
      Date: Wed, 15 Mar 2017 13:48:54 GMT
      
      body=
      {"errorMessage":"Authentication Failed”}
      
      

        Attachments

          Activity

            People

            • Assignee:
              david.luna@forgerock.com David Luna
              Reporter:
              narita.saxena Narita Saxena
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: