Uploaded image for project: 'JBoss Enterprise SOA Platform'
  1. JBoss Enterprise SOA Platform
  2. SOA-3439

modeshape sequencing performance predictability


    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Migrated to another ITS
    • Affects Version/s: 5.2.0.ER4
    • Fix Version/s: None
    • Component/s: EDS
    • Labels:


      Hello, I'm running a script [1] that verifies sequencing is working. It awaits certain amount of time and if data is still not available, it throws. With SOA-P v5.1 seqTimeout in the script was 10 seconds and that was enough time for test to pass. To get a stable behavior I now need to set it to 500 seconds (tried 250 and was not enough). I mean that currently 10 seconds is sometimes enough but sometimes it takes over 250 seconds on a fast machine for sequenced data to become available.

      I am wondering what can cause such difference.

      UPDATE: Actually looking at many test executions, it seems that time is not the issue. Sequencing either happens soon or never. Passed tests never took too much time and in my last test run [2] server didn't sequence even after 500 seconds.

      [1] https://svn.devel.redhat.com/repos/jboss-qa/hudson/config_repository/resources/soa/modeshape/basic-repo-test.war/sequencer_csv.jsp
      [2] https://hudson.qa.jboss.com/hudson/view/SOA-Release/job/soa-eds-plugins-and-adminshell/126/artifact/test-output/Groovy%20Test%20Suite/index.html

        Gliffy Diagrams


            Issue Links



                • Assignee:
                  van.halbert Van Halbert
                  akostadinov Aleksandar Kostadinov
                • Votes:
                  0 Vote for this issue
                  2 Start watching this issue


                  • Created: