Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-18451

Increase JVM heap size for tests in testsuite/domain

XMLWordPrintable

      We have a CI (Olympus) set up which caught test hanging quite often, I can see OOME in the logs. It cannot be reproduced in other CIs , either in local.

      The tests are all in domain testsuites, mainly DomainTestSuite, the logs are like:

      2023-08-30 05:48:22,202 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC000001: Failed to start service 
      jboss.deployment.unit."test.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."test.w
      ar".INSTALL: WFLYSRV0153: Failed to process phase INSTALL of deployment "test.war"
              at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:189)
              at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739)
              at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701)
              at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559)
              at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
              at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990)
              at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
              at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
              at java.lang.Thread.run(Thread.java:750)
      Caused by: java.lang.OutOfMemoryError: GC overhead limit exceeded
              at org.wildfly.extension.undertow.deployment.UndertowDeploymentProcessor.createTldInfo(UndertowDeploymentProces
      sor.java:665)
              at org.wildfly.extension.undertow.deployment.UndertowDeploymentProcessor.createTldsInfo(UndertowDeploymentProce
      ssor.java:600)
              at org.wildfly.extension.undertow.deployment.UndertowDeploymentProcessor.processDeployment(UndertowDeploymentPr
      ocessor.java:331)
              at org.wildfly.extension.undertow.deployment.UndertowDeploymentProcessor.deploy(UndertowDeploymentProcessor.jav
      a:209)
              at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:182)
              ... 8 more
      
      

      During rounds of tests in our CI (Olympus), it was caused by upgrading of bouncycastle from 1.68 to 1.76 ( JBEAP-25101 ) , I also created SET-592 for the investigation.

      Having 100m heap size for the domain testsuite in an environment with high CPU numbers(64) is fragile, Artemis NettyAcceptor will create as 3 * cpus threads which eats much memory.

      So increasing heap size for the tests in domain testsuite looks reasonable.

              rhn-engineering-lgao Lin Gao
              rhn-engineering-lgao Lin Gao
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: