Uploaded image for project: 'Hippo CMS'
  1. Hippo CMS
  2. CMS-3527

CMS locks down completely after a modest load test

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Blocker
    • Resolution: Fixed
    • r2.09.04
    • r2.09.05, r2.11.00
    • None
    • None
    • Linux, Win XP

    Description

      Hi all,

      -------------
      Introduction:
      -------------

      In our acceptance environment we have encountered a bug where the CMS locks down completely after running with ~5 actual concurrent human users.
      In order to narrow down and reproduce this issue, we have taken your quickstart version of the CMS 2.09.04, and applied a simple automated load test which enabled us to reproduce the issue.

      --------------------------
      Reproduction of the issue:
      --------------------------

      We followed the instructions on:

      http://www.onehippo.org/cms7/documentation/quickstart.html

      and downloaded the quickstart from here:

      http://repository.hippocms.org/maven2/org/hippoecm/hippo-ecm-quickstart-bin/2.09.04/hippo-ecm-quickstart-bin-2.09.04.zip

      Without further modifications, we started the CMS quickstart on a developer notebook.

      We used a load testing tool called "Pure Load" (trial version) that allows recording and replaying of http requests.
      See: http://www.minq.se/products/pureload/

      As such, we set up our test to simulate 5 concurrent clients that perform the following steps for an infinite amount of time.
      Note that the scenario below was run from a simple notebook as well.

      • login to the cms under unique user credentials
      • navigate to the news folder
      • create a new newsitem with a unique name (counting up)
      • save the newsitem (including 'done', and closing tab)
      • navigate back to the document root
      • log out of the cms

      Results:

      After running this test setup for 5 to 10 minutes we observe that requests from the load tool no longer are served.
      Trying to login to the CMS from a browser with no running session (clear cache) results in a timeout: the login form does show, login times out...

      Users with a running session in the CMS, are capable of navigating through the CMS without visible issues.
      Logging out such a user, will result in a timeout, trying to logout.

      --------------------------
      Further information:
      --------------------------
      See attachments.

      • Deployment: clean Hippo 7.2 (2.09.04)
      • Tool: PureLoad (free edition, trial version)
      • Test Script: see attachment
      • Nr of workers: 5 (logical names: scenario0 ... scenario4)
      • Nr of threads: 5 (one per worker)

      The script uses five (admin)users in the CMS:

      • dennis0 / dennis0
      • dennis1 / dennis1
      • dennis2 / dennis2
      • dennis3 / dennis3
      • dennis4 / dennis4

      We used a 6th user (just admin/admin) to monitor activity in the CMS while performing the test.

      We are sure you can help us out.
      If you need any more information, let us know.


      Rob van der Linden Vooren | Software Engineer | JTeam | T: +31(0)2-04862036 | www.jteam.nl
      General conditions apply

      Attachments

        1. blocked-threaddump-cachinghierarchymanager.txt
          30 kB
          Bart van der Schans
        2. exception thrown before lock.txt
          8 kB
          Rob van der Linden Vooren
        3. latest-stracktrace.txt
          93 kB
          Rob van der Linden Vooren
        4. log4j.log
          223 kB
          Rob van der Linden Vooren
        5. test-rob-clean-dennis-5-threads-counted.plc
          212 kB
          Rob van der Linden Vooren

        Issue Links

          Activity

            People

              bvdschans Bart van der Schans (Inactive)
              rvooren Rob van der Linden Vooren (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: