org.jboss.as.test.clustering.single.provider.ServiceProviderRegistrationTestCase: org.jboss.as.test.clustering.single.singleton.SingletonServiceTestCase: java.lang.RuntimeException: Arquillian has previously been attempted initialized, but failed. See cause for previous exception To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration

GitHub | wildfly-ci | 2 years ago
tip
Your exception is missing from the Samebug knowledge base.
Here are the best solutions we found on the Internet.
Click on the to mark the helpful solution and get rewards for you help.
  1. 0

    GitHub comment 7985#134488502

    GitHub | 2 years ago | wildfly-ci
    org.jboss.as.test.clustering.single.provider.ServiceProviderRegistrationTestCase: org.jboss.as.test.clustering.single.singleton.SingletonServiceTestCase: java.lang.RuntimeException: Arquillian has previously been attempted initialized, but failed. See cause for previous exception To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration
  2. 0

    GitHub comment 7992#136835936

    GitHub | 2 years ago | wildfly-ci
    org.jboss.as.test.clustering.single.provider.ServiceProviderRegistrationTestCase: org.jboss.as.test.clustering.single.singleton.SingletonServiceTestCase: java.lang.RuntimeException: Arquillian has previously been attempted initialized, but failed. See cause for previous exception To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration
  3. 0

    GitHub comment 8019#137142724

    GitHub | 2 years ago | wildfly-ci
    org.jboss.as.test.clustering.single.provider.ServiceProviderRegistrationTestCase: org.jboss.as.test.clustering.single.singleton.SingletonServiceTestCase: java.lang.RuntimeException: Arquillian has previously been attempted initialized, but failed. See cause for previous exception To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. org.jboss.as.test.clustering.single.provider.ServiceProviderRegistrationTestCase

      org.jboss.as.test.clustering.single.singleton.SingletonServiceTestCase: java.lang.RuntimeException: Arquillian has previously been attempted initialized, but failed. See cause for previous exception To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration

      at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.failDueToRunning()
    2. JBoss Application Server: Arquillian Managed Container
      ManagedDeployableContainer.startInternal
      1. org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.failDueToRunning(ManagedDeployableContainer.java:309)
      2. org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:80)
      2 frames
    3. JBoss Application Server: Arquillian Common
      CommonDeployableContainer.start
      1. org.jboss.as.arquillian.container.CommonDeployableContainer.start(CommonDeployableContainer.java:110)
      1 frame