org.jboss.as.test.integration.domain.mixed.eap630.KernelBehavior630TestSuite

java.lang.RuntimeException: java.lang.RuntimeException: Could not start container

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web12

  • via GitHub by wildfly-ci
    , 11 months ago
    java.lang.RuntimeException: java.lang.RuntimeException: Could not start container
  • via GitHub by wildfly-ci
    , 11 months ago
    org.jboss.as.test.integration.domain.mixed.eap620.LegacyConfig620TestSuite: java.lang.RuntimeException: java.lang.RuntimeException: java.lang.RuntimeException: Could not start container
  • via GitHub by wildfly-ci
    , 11 months ago
    org.jboss.as.test.integration.domain.mixed.eap620.MixedDomain620TestSuite: java.lang.RuntimeException: java.lang.RuntimeException: java.lang.RuntimeException: Could not start container
  • Stack trace

    • org.jboss.as.test.integration.domain.mixed.eap630.KernelBehavior630TestSuite: java.lang.RuntimeException: java.lang.RuntimeException: Could not start container at org.jboss.as.test.integration.domain.management.util.DomainLifecycleUtil.awaitServers(DomainLifecycleUtil.java:449) at org.jboss.as.test.integration.domain.management.util.DomainLifecycleUtil.start(DomainLifecycleUtil.java:251) at org.jboss.as.test.integration.domain.management.util.DomainTestSupport.start(DomainTestSupport.java:369) at org.jboss.as.test.integration.domain.mixed.MixedDomainTestSupport.start(MixedDomainTestSupport.java:88) at org.jboss.as.test.integration.domain.mixed.MixedDomainTestSuite.getSupport(MixedDomainTestSuite.java:96) at org.jboss.as.test.integration.domain.mixed.KernelBehaviorTestSuite.getSupport(KernelBehaviorTestSuite.java:40) at org.jboss.as.test.integration.domain.mixed.eap630.KernelBehavior630TestSuite.initializeDomain(KernelBehavior630TestSuite.java:44)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    You’re the first here who have seen this exception.