Uploaded image for project: 'Arquillian'
  1. Arquillian
  2. ARQ-2205

TimeoutException while running arquillian in EAP 7.2

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: JBoss AS Containers
    • Labels:
      None
    • Steps to Reproduce:
      Hide

      Migrated arquillian from EAP 6 to EAP 7 and it starts failing with timeout error.

      Show
      Migrated arquillian from EAP 6 to EAP 7 and it starts failing with timeout error.

      Description

      18:47:55,246 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: JBoss EAP 7.2.5.GA (WildFly Core 6.0.20.Final-redhat-00001) started in 11702ms - Started 391 of 612 services (377 services are lazy, passive or on-demand)

      Stack trace is:
      Migrated arquillian from EAP 6 to EAP 7 and it starts failing with timeout error.

      Running com.xxx.oss.notification.cache.testsuite.xxxTest
      Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.028 sec <<< FAILURE! - in com.xxx.oss.notification.cache.testsuite.xxxTest
      com.xxx.oss.notification.cache.testsuite.xxxTest
      Time elapsed: 0.028 sec <<< ERROR!
      org.jboss.arquillian.container.spi.client.container.LifecycleException: Could not start container
      Caused by: java.util.concurrent.TimeoutException: Managed server was not started within [7200] s

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                akshay_jboss Akshay Ballarpure
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated: