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

GitHub | wildfly-ci | 2 years ago
  1. 0

    [WFLY-3045] : Expose JAXRS deployments via the management API by ehsavoie · Pull Request #6451 · wildfly/wildfly · GitHub

    github.com | 12 months ago
    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
  2. 0

    GitHub comment 6451#66048876

    GitHub | 2 years ago | 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
  3. 0

    GitHub comment 7111#71020092

    GitHub | 2 years ago | 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
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    GitHub comment 6149#40087487

    GitHub | 3 years ago | 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
  6. 0

    GitHub comment 6150#40042622

    GitHub | 3 years ago | 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

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. 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()
    2. JBoss Application Server: Arquillian Managed Container
      ManagedDeployableContainer.failDueToRunning
      1. org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.failDueToRunning(ManagedDeployableContainer.java:309)
      1 frame