org.wildfly.test.integration.security.picketlink.federation.SAMLRedirectBindingWithSignaturesTestCase: org.wildfly.test.integration.security.picketlink.core.PartitionManagerProducerTestCase: org.jboss.arquillian.container.spi.client.container.LifecycleException: Could not start container

GitHub | wildfly-ci | 3 years ago
tip
Click on the to mark the solution that helps you, Samebug will learn from it.
As a community member, you’ll be rewarded for you help.
  1. 0

    GitHub comment 6855#60137132

    GitHub | 3 years ago | wildfly-ci
    org.wildfly.test.integration.security.picketlink.federation.SAMLRedirectBindingWithSignaturesTestCase: org.wildfly.test.integration.security.picketlink.core.PartitionManagerProducerTestCase: org.jboss.arquillian.container.spi.client.container.LifecycleException: Could not start container

    Root Cause Analysis

    1. org.wildfly.test.integration.security.picketlink.federation.SAMLRedirectBindingWithSignaturesTestCase

      org.wildfly.test.integration.security.picketlink.core.PartitionManagerProducerTestCase: org.jboss.arquillian.container.spi.client.container.LifecycleException: Could not start container

      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:208)
      1 frame
    3. JBoss Application Server: Arquillian Common
      CommonDeployableContainer.start
      1. org.jboss.as.arquillian.container.CommonDeployableContainer.start(CommonDeployableContainer.java:112)
      1 frame