org.jboss.as.test.clustering.single.web.SimpleWebTestCase

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 7111#71029099
    via GitHub by wildfly-ci
    ,
  • GitHub comment 5579#30065526
    via GitHub by wildfly-ci
    ,
  • GitHub comment 5535#29951374
    via GitHub by wildfly-ci
    ,
  • GitHub comment 5567#29836812
    via GitHub by wildfly-ci
    ,
  • GitHub comment 5601#30693913
    via GitHub by wildfly-ci
    ,
  • GitHub comment 5607#30699384
    via GitHub by wildfly-ci
    ,
  • GitHub comment 5673#31695428
    via GitHub by wildfly-ci
    ,
  • GitHub comment 5642#31567161
    via GitHub by wildfly-ci
    ,
  • GitHub comment 5629#31037353
    via GitHub by wildfly-ci
    ,
  • GitHub comment 5640#30989296
    via GitHub by wildfly-ci
    ,
    • org.jboss.as.test.clustering.single.web.SimpleWebTestCase: org.jboss.as.test.clustering.single.dispatcher.CommandDispatcherTestCase: 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.