org.jboss.as.test.clustering.single.provider.ServiceProviderRegistrationTestCase: org.jboss.as.test.clustering.single.dispatcher.CommandDispatcherTestCase: 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

There are no available Samebug tips for this exception. Do you have an idea how to solve this issue? A short tip would help users who saw this issue last week.

  • GitHub comment 8019#137142724
    via GitHub by wildfly-ci
    ,
  • GitHub comment 7985#134488502
    via GitHub by wildfly-ci
    ,
  • GitHub comment 7992#136835936
    via GitHub by wildfly-ci
    ,
    • org.jboss.as.test.clustering.single.provider.ServiceProviderRegistrationTestCase: org.jboss.as.test.clustering.single.dispatcher.CommandDispatcherTestCase: 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(ManagedDeployableContainer.java:312) at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:80) at org.jboss.as.arquillian.container.CommonDeployableContainer.start(CommonDeployableContainer.java:110)
    No Bugmate found.