2 Replies Latest reply: Mar 13, 2012 10:39 AM by Aslak Knutsen RSS

    Error Executing Arquillian Test on JBoss EAP 5.1.1

    Abhishek Shukla Newbie

      I have Arquillian Test that works well on JBoss EAP 5.1.0, but when I execute the same testcase against JBoss EAP 5.1.1 I get the following Container Exception.

       

      org.jboss.arquillian.container.spi.client.container.LifecycleException: Could not connect to container

      at org.jboss.arquillian.container.jbossas.remote_5_1.JBossASRemoteContainer.start(JBossASRemoteContainer.java:92)

      at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$5.perform(ContainerLifecycleController.java:144)

      at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$5.perform(ContainerLifecycleController.java:134)

      at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forContainer(ContainerLifecycleController.java:186)

      at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startContainer(ContainerLifecycleController.java:133)

      ...

      Caused by: java.lang.SecurityException: Authentication exception, principal=null

      at org.jboss.aspects.security.AuthenticationInterceptor.authenticate(AuthenticationInterceptor.java:142)

      at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:69)

      at org.jboss.profileservice.remoting.SecurityContainer.invoke(SecurityContainer.java:75)

      at $Proxy195.getDeploymentManager(Unknown Source)

      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

      at java.lang.reflect.Method.invoke(Method.java:597)

      at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:121)

      at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82)

      at org.jboss.profileservice.remoting.ProfileServiceInvocationHandler.invoke(ProfileServiceInvocationHandler.java:99)

      ...

      I saw a related thread https://community.jboss.org/thread/171332, that makes me think some of my dependencies should change, but not sure to what...

       

      Here's my POM dependencies for Arquillian:

          <dependency>

                    <groupId>org.jboss.jbossas</groupId>

                    <artifactId>jbossall-client</artifactId>

                    <version>5.1.0.GA-eap5_1_0</version>

                    <type>pom</type>

                    <scope>test</scope>

      </dependency>

      <dependency>

          <groupId>org.jboss.arquillian.container</groupId>

          <artifactId>arquillian-jbossas-remote-5.1</artifactId>

          <version>1.0.0.CR2</version>

          <scope>test</scope>

          </dependency>

       



      <dependency>



      <groupId>org.jboss.arquillian.junit</groupId>



      <artifactId>arquillian-junit-container</artifactId>



      <scope>provided</scope>


      </dependency>

       


      <dependencyManagement>


      <dependencies>



      <dependency>


        <groupId>org.jboss.arquillian</groupId>


        <artifactId>arquillian-bom</artifactId>


        <version>1.0.0.CR2</version>


        <scope>import</scope>


        <type>pom</type>


        <optional>true</optional>



      </dependency>


      </dependencies>

      </dependencyManagement>