4:42 p.m.
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
4:58 p.m.
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(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
5 p.m.
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(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
5:02 p.m.
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(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>
>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
5:08 p.m.
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(a)lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>
>>
>> _______________________________________________
>> jboss-as7-dev mailing list
>> jboss-as7-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>
>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
2:52 p.m.
It happens to me on integration.osgi & integration.resource as well.
The problem is deeper than just the ejb3 services, we just manage to
expose it more profoundly. ;-)
Carlo
On 05/04/2011 05:08 PM, Alexey Loubyansky wrote:
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(a)lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>>
>>> _______________________________________________
>>> jboss-as7-dev mailing list
>>> jboss-as7-dev(a)lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>
>> _______________________________________________
>> jboss-as7-dev mailing list
>> jboss-as7-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
3:30 p.m.
That's so inappropriate... But true, there are a few occasional others.
On 05/09/2011 02:52 PM, Carlo de Wolf wrote:
It happens to me on integration.osgi & integration.resource as
well.
The problem is deeper than just the ejb3 services, we just manage to
expose it more profoundly. ;-)
Carlo
On 05/04/2011 05:08 PM, Alexey Loubyansky wrote:
> 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(a)lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>>>
>>>> _______________________________________________
>>>> jboss-as7-dev mailing list
>>>> jboss-as7-dev(a)lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>>
>>> _______________________________________________
>>> jboss-as7-dev mailing list
>>> jboss-as7-dev(a)lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>> _______________________________________________
>> jboss-as7-dev mailing list
>> jboss-as7-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
12:22 a.m.
I am pretty sure I know what causes this.
The server figures out if a deployment is complete in
ServierControllerImpl.ServerStateMonitorListener, however there are situations where a
race condition can occur that causes the listener to think the deployment is finished
before it is actually done.
For example, it is possible for the listener to see the dependencyProblemCleared event
before the dependencyProblem event takes place, this can cause the tick count to hit zero
even though the deployment is still underway (I am pretty sure there are other race
conditions as well).
These problems show up in the EE subsystem more than any other, as the EE subsystem
installs a lot of it's services out of order (i.e. before all corresponding deps are
installed), which generates a lot more of the dependencyProblem and
dependencyProblemCleared events.
Stuart
On 09/05/2011, at 11:30 PM, Alexey Loubyansky wrote:
That's so inappropriate... But true, there are a few occasional
others.
On 05/09/2011 02:52 PM, Carlo de Wolf wrote:
> It happens to me on integration.osgi & integration.resource as well.
> The problem is deeper than just the ejb3 services, we just manage to
> expose it more profoundly. ;-)
>
> Carlo
>
> On 05/04/2011 05:08 PM, Alexey Loubyansky wrote:
>> 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(a)lists.jboss.org
>>>>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>>>>
>>>>> _______________________________________________
>>>>> jboss-as7-dev mailing list
>>>>> jboss-as7-dev(a)lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>>>
>>>> _______________________________________________
>>>> jboss-as7-dev mailing list
>>>> jboss-as7-dev(a)lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>> _______________________________________________
>>> jboss-as7-dev mailing list
>>> jboss-as7-dev(a)lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>> _______________________________________________
>> jboss-as7-dev mailing list
>> jboss-as7-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
3:36 p.m.
I've created integration testsuite jobs on Hudson against different platforms. Each
one yields different results.
http://hudson.jboss.org/hudson/job/JBoss-AS-7.0.x-testSuite-sun16/ (Linux)
http://hudson.jboss.org/hudson/job/JBoss-AS-7.0.x-testSuite-windows/
http://hudson.jboss.org/hudson/job/JBoss-AS-7.0.x-Solaris/
http://hudson.jboss.org/hudson/job/JBoss-AS-7.0.x-testSuite-openjdk/
The windows job seems to be the most accurate.
Shelly McGowan
JBoss, by Red Hat
----- Original Message -----
From: "Stuart Douglas" <stuart.w.douglas(a)gmail.com>
To: "Alexey Loubyansky" <alexey.loubyansky(a)redhat.com>
Cc: jboss-as7-dev(a)lists.jboss.org
Sent: Monday, May 9, 2011 6:22:33 PM
Subject: Re: [jboss-as7-dev] sporadic testsuite failures
I am pretty sure I know what causes this.
The server figures out if a deployment is complete in
ServierControllerImpl.ServerStateMonitorListener, however there are situations where a
race condition can occur that causes the listener to think the deployment is finished
before it is actually done.
For example, it is possible for the listener to see the dependencyProblemCleared event
before the dependencyProblem event takes place, this can cause the tick count to hit zero
even though the deployment is still underway (I am pretty sure there are other race
conditions as well).
These problems show up in the EE subsystem more than any other, as the EE subsystem
installs a lot of it's services out of order (i.e. before all corresponding deps are
installed), which generates a lot more of the dependencyProblem and
dependencyProblemCleared events.
Stuart
On 09/05/2011, at 11:30 PM, Alexey Loubyansky wrote:
That's so inappropriate... But true, there are a few occasional
others.
On 05/09/2011 02:52 PM, Carlo de Wolf wrote:
> It happens to me on integration.osgi & integration.resource as well.
> The problem is deeper than just the ejb3 services, we just manage to
> expose it more profoundly. ;-)
>
> Carlo
>
> On 05/04/2011 05:08 PM, Alexey Loubyansky wrote:
>> 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(a)lists.jboss.org
>>>>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>>>>
>>>>> _______________________________________________
>>>>> jboss-as7-dev mailing list
>>>>> jboss-as7-dev(a)lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>>>
>>>> _______________________________________________
>>>> jboss-as7-dev mailing list
>>>> jboss-as7-dev(a)lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>> _______________________________________________
>>> jboss-as7-dev mailing list
>>> jboss-as7-dev(a)lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>> _______________________________________________
>> jboss-as7-dev mailing list
>> jboss-as7-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
4733
days inactive
4741
days old
8 comments
6 participants
participants (6)
-
Alexey Loubyansky -
Carlo de Wolf -
Jaikiran Pai -
Kabir Khan -
Shelly McGowan -
Stuart Douglas