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

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 7458#102394100
    via GitHub by liweinan
    ,
  • GitHub comment 4758#20745359
    via GitHub by wildfly-ci
    ,
  • GitHub comment 4795#21076299
    via GitHub by wildfly-ci
    ,
  • GitHub comment 4795#21076365
    via GitHub by wildfly-ci
    ,
  • GitHub comment 5315#26740552
    via GitHub by wildfly-ci
    ,
  • GitHub comment 5332#26916116
    via GitHub by wildfly-ci
    ,
  • GitHub comment 5415#27819811
    via GitHub by wildfly-ci
    ,
  • GitHub comment 5393#27514701
    via GitHub by wildfly-ci
    ,
  • GitHub comment 5454#28307875
    via GitHub by wildfly-ci
    ,
  • GitHub comment 5371#28278875
    via GitHub by wildfly-ci
    ,
    • 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)

    Users with the same issue

    Andreas Häber
    Andreas Häber3 times, last one,