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 | 2 years ago
tip
Your exception is missing from the Samebug knowledge base.
Here are the best solutions we found on the Internet.
Click on the to mark the helpful solution and get rewards for you help.
  1. 0

    GitHub comment 6855#60137132

    GitHub | 2 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