[wildfly-dev] ARQ container cannot fetch deployment from client side any more

[Darran Lofthouse]

I will see if I can reproduce - we have had minor Remoting JMX updates.

Regards,
Darran Lofthouse.


On 06/09/13 12:04, Thomas Diesler wrote:
> I see it with the jbosgi integration tests against the latest wildfly master
>
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBossOSGi/job/jbosgi-wildfly-master/55/console
>
> There have been no changes on my side.
>
> cheers
> --thomas
>
> On Sep 6, 2013, at 12:58 PM, Darran Lofthouse
> <darran.lofthouse at jboss.com <mailto:darran.lofthouse at jboss.com>> wrote:
>
>> Hi Thomas,
>>
>> Is this something easily reproducible?
>>
>> Regards,
>> Darran Lofthouse.
>>
>>
>> On 06/09/13 11:56, Thomas Diesler wrote:
>>> Folks,
>>>
>>> lately lots of wildfly integration tests fail because the ARQ service
>>> cannot fetch a deployment from the client side any more
>>>
>>> java.lang.RuntimeException: Could not communicate with client side
>>> at
>>> org.jboss.arquillian.protocol.jmx.JMXCommandService.execute(JMXCommandService.java:60)
>>> at
>>> org.jboss.arquillian.container.test.impl.client.deployment.ContainerDeployer.getDeployment(ContainerDeployer.java:58)
>>>
>>> would you know what causes this?
>>>
>>> cheers
>>> --thomas
>>> _______________________________________________
>>> wildfly-dev mailing list
>>> wildfly-dev at lists.jboss.org <mailto:wildfly-dev at lists.jboss.org>
>>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>>
>> _______________________________________________
>> wildfly-dev mailing list
>> wildfly-dev at lists.jboss.org <mailto:wildfly-dev at lists.jboss.org>
>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>