org.jboss.as.test.iiop.transaction.TransactionIIOPInvocationTestCase: org.jboss.as.test.iiop.basic.BasicIIOPInvocationTestCase: 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
tip
Do you know that we can give you better hits? Get more relevant results from Samebug’s stack trace search.
  1. 0

    GitHub comment 6840#60286337

    GitHub | 2 years ago | wildfly-ci
    org.jboss.as.test.iiop.transaction.TransactionIIOPInvocationTestCase: org.jboss.as.test.iiop.basic.BasicIIOPInvocationTestCase: 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 6840#60240441

    GitHub | 2 years ago | wildfly-ci
    org.jboss.as.test.iiop.transaction.TransactionIIOPInvocationTestCase: org.jboss.as.test.iiop.basic.BasicIIOPInvocationTestCase: 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 6840#60159669

    GitHub | 2 years ago | wildfly-ci
    org.jboss.as.test.iiop.transaction.TransactionIIOPInvocationTestCase: org.jboss.as.test.iiop.basic.BasicIIOPInvocationTestCase: 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

    Root Cause Analysis

    1. org.jboss.as.test.iiop.transaction.TransactionIIOPInvocationTestCase

      org.jboss.as.test.iiop.basic.BasicIIOPInvocationTestCase: 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:358)
      1 frame