|Re: can not run test with remote aut agent [message #1717151 is a reply to message #1716954]
||Thu, 10 December 2015 10:15
| Luca Da Rin Fioretto
Registered: November 2015
Oliver Goetz wrote on Wed, 09 December 2015 09:43|
do the log-files contain any useful Information? You can find them in <YourHomeDirectory>/<.jubula>/<logs>.
Thank you Oliver,
I was able to solve the problem, but the following might be useful for others in my situation.
My system has three virtual machines running different Linux distros guests on VirtualBox on a Windows 8 host OS. Each machine is configured with two network adapters, a NAT as primary and a Host-Only as secondary. They can talk betbeen each other on the Host-Only private network as they're all in the same subnet.
The way Jubula handle remote AUT connections is described at (add http) testing.bredex.de/faqs/what-connections-are-required-between-the-ite-and-the-aut-agent.html. (I can't as the forum is preventing me from posting URLs as I don't have more than 5 posts. But let's continue.) So what happened on my system is that the machine running the testexec process was able to successfully call the remote autagent but then the AUT wasn't able to reach back the testexec process as shown in the log produced by the AUT (<HomeDirectory>/<.jubula>/<logs>) below:
2015-12-08 16:53:48.001 [Connection.ReaderThread:Socket[addr=localhost/127.0.0.1,port=58415,localport=53721]] ERROR o.e.j.r.c.c.ConnectToClientCommand - Error while attempting to connect to client.
java.net.UnknownHostException: controller: unknown error
at java.net.Inet6AddressImpl.lookupAllHostAddr(Native Method) ~[na:1.8.0_66]
at java.net.InetAddress$2.lookupAllHostAddr(InetAddress.java:928) ~[na:1.8.0_66]
at java.net.InetAddress.getAddressesFromNameService(InetAddress.java:1323) ~[na:1.8.0_66]
at java.net.InetAddress.getAllByName0(InetAddress.java:1276) ~[na:1.8.0_66]
at java.net.InetAddress.getAllByName(InetAddress.java:1192) ~[na:1.8.0_66]
at java.net.InetAddress.getAllByName(InetAddress.java:1126) ~[na:1.8.0_66]
at java.net.InetAddress.getByName(InetAddress.java:1076) ~[na:1.8.0_66]
at org.eclipse.jubula.rc.common.AUTServer.initClientCommunication(AUTServer.java:511) ~[org.eclipse.jubula.rc.common.jar:na]
at org.eclipse.jubula.rc.common.commands.ConnectToClientCommand.execute(ConnectToClientCommand.java:41) ~[org.eclipse.jubula.rc.common.jar:na]
at org.eclipse.jubula.communication.internal.Communicator$ConnectionListener.received(Communicator.java:918) [org.eclipse.jubula.communication.jar:na]
at org.eclipse.jubula.communication.internal.connection.Connection.fireMessageReceived(Connection.java:402) [org.eclipse.jubula.communication.jar:na]
at org.eclipse.jubula.communication.internal.connection.Connection.access$2(Connection.java:391) [org.eclipse.jubula.communication.jar:na]
at org.eclipse.jubula.communication.internal.connection.Connection$ReaderThread.run(Connection.java:454) [org.eclipse.jubula.communication.jar:na]
Where "controller" is the hostname of the machine running the testexec. Looks to me that the AUT machine is trying to contact "controller" instead of the private IP of the testexec machine. Hence if you don't have a DNS on your system this won't work. So the way I solved the problem is by modifying the primary network interface of the testexec machine from NAT to bridged.
[Updated on: Fri, 11 December 2015 18:05]
Report message to a moderator
Powered by FUDForum
. Page generated in 0.10315 seconds