Uploaded image for project: 'PUBLIC - Liferay Portal Community Edition'
  1. PUBLIC - Liferay Portal Community Edition
  2. LPS-86623

Running tests on Wildfly uncovers OutOfMemory and other server-related errors

    Details

    • Fix Priority:
      3

      Description

      It looks like the tests on the Wildfly run may still require more time after start-app-server finishes a second time (a requirement of running Audience Targeting, as it needs to bounce the server to complete the installation), before starting the poshi testcase.

      Looking into ContentTargetingUserSegment#EditUserSegmentCP, the Poshi Report shows that the server isn't ready by the time the User would sign in on the Poshi test, but when opening /web/guest/home in the teardown, the server finally does return the home page.

      The Jenkins Log looks fine, as the second start-app-server call waits until after this is shown in the log before embarking on the testcase:

      WildFly Full 10.0.0.Final (WildFly Core 2.0.10.Final) started in 194904ms - Started 2565 of 2853 services (378 services are lazy, passive or on-demand)
      

      Adding a hardcoded pause before the test starts up will probably fix this issue.

        Attachments

          Activity

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:
                Days since last comment:
                14 weeks, 5 days ago

                Packages

                Version Package