[jboss-as7-dev] sporadic testsuite failures

[Alexey Loubyansky]

Actually, it's been annoying me for weeks now. Let me know if you need 
more details.

Thanks,
Alexey

On 05/04/2011 05:02 PM, Jaikiran Pai wrote:
> I haven't yet seen these failures, locally. Let me try running it a few
> times and see if I can reproduce these.
>
> -Jaikiran
> On Wednesday 04 May 2011 08:30 PM, Kabir Khan wrote:
>> The first few tests against the running server pass:
>> Running org.jboss.as.test.spec.servlet3.WebSecurityProgrammaticLoginTestCase
>> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 8.923 sec
>> Running org.jboss.as.test.spec.ejb3.StatelessBeanTestCase
>> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.296 sec
>> Running org.jboss.as.test.spec.ejb3.SlsbTestCase
>> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 1.793 sec<<<   FAILURE!
>> Running org.jboss.as.test.spec.ejb3.SingletonBeanTestCase
>> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 1.361 sec<<<   FAILURE!
>> Running org.jboss.as.test.spec.ejb3.AsyncBeanTestCase
>> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 1.593 sec<<<   FAILURE!
>> Running org.jboss.as.test.spec.ejb3.StatefulBeanTestCase
>> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 1.665 sec<<<   FAILURE!
>>
>> On 4 May 2011, at 15:58, Kabir Khan wrote:
>>
>>> They fail sometimes for me as well. For org.jboss.as.test.spec.ejb3.SlsbTestCase the root exception is, so it sounds like some concurrency issue setting up the EJB 3 services
>>>
>>> Caused by: java.util.concurrent.ExecutionException: java.lang.Exception: {
>>>      "New missing/unsatisfied dependencies" =>   [
>>>          "service jboss.naming.context.java.comp.test.test.GreeterSlsb (missing)",
>>>          "service jboss.naming.context.java.module.test.test (missing)"
>>>      ],
>>>      "Services which failed to start:" =>   ["service jboss.deployment.unit.\"test.war\".INSTALL"]
>>> }
>>>          at org.jboss.as.controller.client.helpers.standalone.impl.ModelControllerClientServerDeploymentManager$Handler.getResult(ModelControllerClientServerDeploymentManager.java:199)
>>>          at org.jboss.as.controller.client.helpers.standalone.impl.ModelControllerClientServerDeploymentManager$Handler.get(ModelControllerClientServerDeploymentManager.java:167)
>>>          at org.jboss.as.controller.client.helpers.standalone.impl.ModelControllerClientServerDeploymentManager$Handler.get(ModelControllerClientServerDeploymentManager.java:64)
>>>          at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.get(ServerDeploymentPlanResultFuture.java:68)
>>>          at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.get(ServerDeploymentPlanResultFuture.java:41)
>>>          at org.jboss.as.arquillian.container.AbstractDeployableContainer.executeDeploymentPlan(AbstractDeployableContainer.java:169)
>>>          at org.jboss.as.arquillian.container.AbstractDeployableContainer.deploy(AbstractDeployableContainer.java:158)
>>>          ... 91 more
>>> Caused by: java.lang.Exception: {
>>>      "New missing/unsatisfied dependencies" =>   [
>>>          "service jboss.naming.context.java.comp.test.test.GreeterSlsb (missing)",
>>>          "service jboss.naming.context.java.module.test.test (missing)"
>>>      ],
>>>      "Services which failed to start:" =>   ["service jboss.deployment.unit.\"test.war\".INSTALL"]
>>> }
>>>          at org.jboss.as.controller.client.helpers.standalone.impl.ModelControllerClientServerDeploymentManager$Handler$1.handleFailed(ModelControllerClientServerDeploymentManager.java:105)
>>>          at org.jboss.as.controller.client.AbstractModelControllerClient$ExecuteAsynchronousRequest.receiveResponse(AbstractModelControllerClient.java:279)
>>>          at org.jboss.as.controller.client.AbstractModelControllerClient$ExecuteAsynchronousRequest.receiveResponse(AbstractModelControllerClient.java:228)
>>>          at org.jboss.as.protocol.mgmt.ManagementRequest$2.handle(ManagementRequest.java:226)
>>>          at org.jboss.as.protocol.mgmt.AbstractMessageHandler.handleMessage(AbstractMessageHandler.java:63)
>>>          at org.jboss.as.protocol.ConnectionImpl.safeHandleMessage(ConnectionImpl.java:274)
>>>          at org.jboss.as.protocol.ConnectionImpl$1$1.run(ConnectionImpl.java:228)
>>>          at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>>>          at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>>>          at java.lang.Thread.run(Thread.java:680)
>>>          at org.jboss.threads.JBossThread.run(JBossThread.java:122)
>>>
>>>
>>>
>>>
>>> On 4 May 2011, at 15:42, Alexey Loubyansky wrote:
>>>
>>>> Is anybody looking into them? Is the issue in the AS codebase or the tests?
>>>> Most often it's a few ejb3 tests.
>>>>
>>>> Thanks,
>>>> Alexey
>>>> _______________________________________________
>>>> jboss-as7-dev mailing list
>>>> jboss-as7-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>>
>>>
>>> _______________________________________________
>>> jboss-as7-dev mailing list
>>> jboss-as7-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>
>>
>> _______________________________________________
>> jboss-as7-dev mailing list
>> jboss-as7-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev