org.jboss.as.test.clustering.single.registry.RegistryTestCase

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 6451#66048876
    via GitHub by wildfly-ci
    ,
  • GitHub comment 7111#71020092
    via GitHub by wildfly-ci
    ,
  • GitHub comment 6149#40087487
    via GitHub by wildfly-ci
    ,
  • GitHub comment 6150#40042622
    via GitHub by wildfly-ci
    ,
  • GitHub comment 6580#51817472
    via GitHub by wildfly-ci
    ,
  • GitHub comment 6419#53306108
    via GitHub by wildfly-ci
    ,
  • GitHub comment 6598#52241147
    via GitHub by wildfly-ci
    ,
  • GitHub comment 6634#53499270
    via GitHub by wildfly-ci
    ,
    • org.jboss.as.test.clustering.single.registry.RegistryTestCase: org.jboss.as.test.clustering.single.singleton.SingletonServiceTestCase: org.jboss.arquillian.container.spi.client.container.LifecycleException: The server is already running! Managed containers do not support connecting to running server instances due to the possible harmful effect of connecting to the wrong server. Please stop server before running or change to another type of container. 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:309)
    No Bugmate found.