org.jboss.as.test.iiop.security.IIOPSecurityInvocationTestCase: java.lang.RuntimeException: Arquillian has previously been attempted initialized, but failed. See cause for previous exception

GitHub | wildfly-ci | 8 months 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 9157#243362210

    GitHub | 8 months ago | wildfly-ci
    org.jboss.as.test.iiop.security.IIOPSecurityInvocationTestCase: java.lang.RuntimeException: Arquillian has previously been attempted initialized, but failed. See cause for previous exception
  2. 0

    GitHub comment 9140#243356074

    GitHub | 8 months ago | wildfly-ci
    org.jboss.as.test.iiop.security.IIOPSecurityInvocationTestCase: java.lang.RuntimeException: Arquillian has previously been attempted initialized, but failed. See cause for previous exception To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration

    Root Cause Analysis

    1. org.jboss.as.test.iiop.security.IIOPSecurityInvocationTestCase

      java.lang.RuntimeException: Arquillian has previously been attempted initialized, but failed. See cause for previous exception

      at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal()
    2. JBoss Application Server: Arquillian Managed Container
      ManagedDeployableContainer.startInternal
      1. org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:152)
      1 frame
    3. JBoss Application Server: Arquillian Common
      CommonDeployableContainer.start
      1. org.jboss.as.arquillian.container.CommonDeployableContainer.start(CommonDeployableContainer.java:115)
      1 frame