[arquillian-issues] [JBoss JIRA] Commented: (ARQ-359) Support testing against remote JBoss AS on different hostname / machine

[Ronny Fraunhofer (JIRA)]

    [ https://issues.jboss.org/browse/ARQ-359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12585005#comment-12585005 ] 

Ronny Fraunhofer commented on ARQ-359:
--------------------------------------

I think the problem lies in resolving the clients ip-address by name.
In my case my client has two network adaptors. One of them can be resolved via DHCP so the remote servers knows this address.
The other network adaptor is the microsoft loopback adaptor (i'm using windows 7).
When creating the http-connection everything works fine.
But when creating the sockets (using bisocket for the InvokerConfiguration), the algorithm to resolve the ip-address takes the first address it can find for client's hostname.
This is the failure.

Either you disable the 'wrong' network adaptor or enable to configure the client by the ip-address not by the hostname.

> Support testing against remote JBoss AS on different hostname / machine
> -----------------------------------------------------------------------
>
>                 Key: ARQ-359
>                 URL: https://issues.jboss.org/browse/ARQ-359
>             Project: Arquillian
>          Issue Type: Feature Request
>          Components: JBoss Containers
>    Affects Versions: 1.0.0.Alpha4
>            Reporter: Dan Allen
>
> Support testing against remote JBoss AS on different hostname / machine. Even though it's possible to configure the remote JBoss AS adapter to point to another address, tests fail because of a reverse lookup error in the JBoss AS server invoker. Assuming hostname is "envy", the following exception occurs during test deployment:
> Caused by: java.lang.RuntimeException: java.io.IOException: Can not get connection to server. Problem establishing socket connection for InvokerLocator [socket://envy: 10234/]
>    at org.jboss.profileservice.management.client.upload.StreamingDeploymentTarget.transferDeployment(StreamingDeploymentTarget.java:286)
>    at org.jboss.profileservice.management.client.upload.StreamingDeploymentTarget.distribute(StreamingDeploymentTarget.java:106)
>    at org.jboss.profileservice.management.client.upload.DeploymentProgressImpl.distribute(DeploymentProgressImpl.java:178)
>    at org.jboss.profileservice.management.client.upload.DeploymentProgressImpl.run(DeploymentProgressImpl.java:83)
>    at org.jboss.arquillian.container.jbossas.remote_6.JBossASRemoteContainer.deploy(JBossASRemoteContainer.java:144)
>    ... 21 more
> Caused by: java.io.IOException: Can not get connection to server. Problem establishing socket connection for InvokerLocator [socket://envy:10234/]
>    at org.jboss.remoting.stream.StreamHandler.read(StreamHandler.java:382)
>    at org.jboss.vfs.VFSUtils.copyStream(VFSUtils.java:426)
>    at org.jboss.vfs.VFSUtils.copyStream(VFSUtils.java:406)
>    at org.jboss.profileservice.repository.artifact.CopyStreamArtifactTransformer.transform(CopyStreamArtifactTransformer.java:59)
>    at org.jboss.profileservice.repository.artifact.file.MutableFileArtifactRepository.addArtifact(MutableFileArtifactRepository.java:92)
>    at org.jboss.profileservice.repository.artifact.file.MutableFileArtifactRepository.addArtifact(MutableFileArtifactRepository.java:46)
>    at org.jboss.profileservice.plugins.deploy.actions.DeploymentDistributeAction.doPrepare(DeploymentDistributeAction.java:108)
>    at org.jboss.profileservice.management.actions.AbstractTwoPhaseModificationAction.prepare(AbstractTwoPhaseModificationAction.java:101)
>    at org.jboss.profileservice.management.ModificationSession.prepare(ModificationSession.java:87)
>    at org.jboss.profileservice.management.AbstractActionController.internalPerfom(AbstractActionController.java:234)
>    at org.jboss.profileservice.management.AbstractActionController.performWrite(AbstractActionController.java:213)
>    at org.jboss.profileservice.management.AbstractActionController.perform(AbstractActionController.java:150)
>    at org.jboss.profileservice.plugins.deploy.AbstractDeployHandler.addDeployment(AbstractDeployHandler.java:133)
>    at org.jboss.profileservice.management.upload.remoting.DeployHandlerDelegate.distribute(DeployHandlerDelegate.java:68)
>    at org.jboss.profileservice.management.upload.remoting.DeployHandler.handleStream(DeployHandler.java:200)
>    at org.jboss.profileservice.management.upload.remoting.DeployHandler.handleStream(DeployHandler.java:55)
>    at org.jboss.remoting.ServerInvoker.handleInternalInvocation(ServerInvoker.java:1809)
> This may depend on an upstream problem in JBoss AS.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira