Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Jubula » Reason 7009: Testexec.exe works localhost but not remote with same config.xml
Reason 7009: Testexec.exe works localhost but not remote with same config.xml [message #910692] Mon, 10 September 2012 08:19 Go to next message
Johann Vogel is currently offline Johann Vogel
Messages: 20
Registered: February 2012
Junior Member
Connecting from remote-host:
D:\jubula_1.2.1\jubula>testexec.exe -c test.xml
Mon Sep 10 09:43:05 CEST 2012   Using configuration file:
        D:\jubula_1.2.1\jubula\test.xml
Mon Sep 10 09:43:06 CEST 2012   AUT Agent:      Connecting to "[censored]:60
000" ...
Mon Sep 10 09:43:07 CEST 2012   AUT Agent:      connection established.
Mon Sep 10 09:43:07 CEST 2012   Database:       Connecting as "JUBULA" to "jdbc:
oracle:thin:@[censored]:1521:TESTDB"...
Mon Sep 10 09:43:10 CEST 2012   Database:       Connection established.
Mon Sep 10 09:43:10 CEST 2012   Database:       Loading project "[censored]_1" in v
ersion "1.0"...
Mon Sep 10 09:43:42 CEST 2012   Database:       Project loading completed.
Mon Sep 10 09:43:42 CEST 2012   Project:        Checking completeness
Mon Sep 10 09:43:42 CEST 2012   Checking completeness of Test Suite "01_login"..
.
Mon Sep 10 09:43:42 CEST 2012   AUT:            Starting AUT: MSS
Mon Sep 10 09:44:46 CEST 2012           Start Test Suite: 01_login
Mon Sep 10 09:44:46 CEST 2012   Executing Test Suite "01_login"...
Mon Sep 10 09:44:46 CEST 2012   Preparing execution of Test Suite "01_login"...
Mon Sep 10 09:44:46 CEST 2012   AUT:            Connecting to "mssstart"...
!!Error occurred !!
        Could not connect to AUT: mssstart

Note: It doesn't even terminate, it keeps hanging in that state.

Connectiong from localhost:
E:\jubula_1.2.1\jubula>testexec.exe -c test.xml
Mon Sep 10 09:52:42 CEST 2012   Using configuration file:
        E:\jubula_1.2.1\jubula\test.xml
Mon Sep 10 09:52:43 CEST 2012   AUT Agent:      Connecting to "[censored]:60
000" ...
Mon Sep 10 09:52:45 CEST 2012   AUT Agent:      connection established.
Mon Sep 10 09:52:45 CEST 2012   Database:       Connecting as "JUBULA" to "jdbc:
oracle:thin:@[censored]:1521:TESTDB"...
Mon Sep 10 09:52:49 CEST 2012   Database:       Connection established.
Mon Sep 10 09:52:49 CEST 2012   Database:       Loading project "[censored]_1" in v
ersion "1.0"...
Mon Sep 10 09:53:18 CEST 2012   Database:       Project loading completed.
Mon Sep 10 09:53:18 CEST 2012   Project:        Checking completeness
Mon Sep 10 09:53:18 CEST 2012   Checking completeness of Test Suite "01_login"..
.
Mon Sep 10 09:53:18 CEST 2012   AUT:            Starting AUT: MSS
Mon Sep 10 09:53:36 CEST 2012           Start Test Suite: 01_login
Mon Sep 10 09:53:36 CEST 2012   Executing Test Suite "01_login"...
Mon Sep 10 09:53:36 CEST 2012   Preparing execution of Test Suite "01_login"...
Mon Sep 10 09:53:36 CEST 2012   AUT:            Connecting to "mssstart"...
Mon Sep 10 09:53:39 CEST 2012   AUT:            Connection established.
Mon Sep 10 09:53:40 CEST 2012   Resolving predefined Variables
Mon Sep 10 09:53:40 CEST 2012   Resolving Test Steps to execute...
Mon Sep 10 09:53:40 CEST 2012   Activating AUT...
Mon Sep 10 09:53:40 CEST 2012   Test Suite "01_login" execution...
...
(and running)

It's the same config file with the same IPs in it, just once started from a remote host and once from localhost, but it doesn't work when executed remote. And the worst thing: the script doesn't even exit at all when it can't find the AUT mssstart, I have to kill it with ctrl+c.

Edit #1: Changing the AUT in MSS@localhost to "MSS" doesn't help.
Mon Sep 10 10:35:15 CEST 2012   AUT:            Starting AUT: MSS
Mon Sep 10 10:35:35 CEST 2012           Start Test Suite: 01_login
Mon Sep 10 10:35:35 CEST 2012   Executing Test Suite "01_login"...
Mon Sep 10 10:35:35 CEST 2012   Preparing execution of Test Suite "01_login"...
Mon Sep 10 10:35:35 CEST 2012   AUT:            Connecting to "MSS"...
!!Error occurred !!
        Could not connect to AUT: MSS



Edit #2: Ok i was able to reproduce the Problem with the GFExplorer and on GUI. Here are the steps:
0. Create some Oracle DB, New Project/Use existing project for that (you already have this)
1. Test -> Properties -> New AUT ->
2. Name it "ex" -> Toolkit RCP -> Add Aut Conf
3. (Basic) -> Host: Add host with your (local) IP, select it (not localhost!)
4. Select GFEExplorer in Examples
5. Create a simple Testcase named "activateEx", just put one Application -> Activate Step into it, Put this Testcase activateEx into a Test suite, choose the ex-application as application in the Properties.
6. Start AUT-Agent from /server (on the IP you just added)
7. Now go to Host #2, start Jubula, load project, connect to the non-local AUT Agent, start ex-aut. Now the GFEExample should start up at Host #1.
8. Start "ActivateEx" from the Test Suite Browser (on Host #2)
9. This error Window, no test is executed.
index.php/fa/11439/0/
(10. Disconnect Aut Agent, try Step 7 + 8 on Host #1 - it works. So some kind of your connection is going local instead of over the network.)

It's the same error as described in the first part, that you can start the AUT but no concrete Test Suite, because the AUT can't be found if it's remote.

Edit #3: Problem also exists with swt/swing applications like the SimpleAdder. It also exists in the 1.1 Version with MySQL.

[Updated on: Mon, 10 September 2012 14:16]

Report message to a moderator

Re: Reason 7009: Testexec.exe works localhost but not remote with same config.xml [message #911370 is a reply to message #910692] Tue, 11 September 2012 13:14 Go to previous messageGo to next message
Alexandra Schladebeck is currently offline Alexandra Schladebeck
Messages: 1153
Registered: July 2009
Senior Member
Hi,

It sounds like it could be a firewall problem - can you check whether that is the case?
HTH,
Alex
Re: Reason 7009: Testexec.exe works localhost but not remote with same config.xml [message #911780 is a reply to message #911370] Wed, 12 September 2012 09:55 Go to previous messageGo to next message
Johann Vogel is currently offline Johann Vogel
Messages: 20
Registered: February 2012
Junior Member
I have considered that too, the firewall is off on both hosts and Host #1 is able to start the AUT itself (on Host #2), so there actually is a working connection, it's just unable to start the test in the AUT.

[Updated on: Wed, 12 September 2012 09:56]

Report message to a moderator

Re: Reason 7009: Testexec.exe works localhost but not remote with same config.xml [message #912288 is a reply to message #911780] Thu, 13 September 2012 09:12 Go to previous messageGo to next message
Alexandra Schladebeck is currently offline Alexandra Schladebeck
Messages: 1153
Registered: July 2009
Senior Member
Hi,

After chatting to the developers, I've put together a picture Smile

The important part in this case is the second page - when we *connect* to an AUT (for test execution or object mapping, for example), then a reverse connection is made back to the host on which the ITE is running. This connection is done via hostname. More information is in the picture, but basically there are three possible points of failure: outgoing connections blocked on the AUT machine, incoming connections blocked on the ITE machine, or no DNS resolution of the hostname for the ITE machine.

HTH,
Alex
Re: Reason 7009: Testexec.exe works localhost but not remote with same config.xml [message #912407 is a reply to message #912288] Thu, 13 September 2012 14:13 Go to previous message
Johann Vogel is currently offline Johann Vogel
Messages: 20
Registered: February 2012
Junior Member
Hi

The problem really was kind of what you described: the ITE machine is in another network than the AUT machine and the ITE is behind a NAT/PAT-Firewall, so it can't be "called back" from the DMZ where all the servers are in. I already have solved (or more worked around) the problem with the help of our build server, that calls the AUT machine to start the AUT on itself.

Although this behavior is quite odd/unexpected because it breaks the expected client-server-pattern by "backconnecting" instead of using an existing connection. I don't really see a need to fix this (lower-version-incompatibilities etc.), but an improved errormessage (at least linking to your explenation) would really help the next users.

Thanks for your answer.
Previous Topic:How to start AUT which is JNLP
Next Topic:Running the Jubula feature on Solaris SPARC/x86
Goto Forum:
  


Current Time: Tue Sep 23 20:32:38 GMT 2014

Powered by FUDForum. Page generated in 0.01632 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software