Community
Participate
Working Groups
Build Identifier: [Connection.ReaderThread:Socket[addr=localhost/127.0.0.1,port=11419,localport=49278]] ERROR o.e.j.c.c.c.StartAUTServerStateCommand - AUTServer could not start: Error while starting AUT! Reproducible: Always Steps to Reproduce: 1. Select a SWT AUT to start
I have changed this to a higher priority because it is affecting the nightly regression tests.
As this bug report does not reference any specific AUT which has been used to reproduce the error I assume that: - it is reproducible with any SWT-AUT - that this assumption also includes our example SWT-AUTs such as the "Simple Adder". I am able to reproduce the error with our example SWT-AUT "Simple Adder": The problem with this AUT is, that due to recent changes the runtime class-path for the executable JAR is wrong. I have fixed this issue: http://git.eclipse.org/c/jubula/org.eclipse.jubula.core.git/commit/?id=fb41946e6d8e97bd4d7323ba077554b4016e005e and http://git.eclipse.org/c/jubula/org.eclipse.jubula.core.git/commit/?id=d8e83ee8954d7fe83b6a9919d7831602f6a60971 Furthermore after resolving this AUT related issue the previously mentioned SWT AUT starts without any problems. I also recognized that our example project AUT launch configuration still make use of the no longer necessary "-Djava.ext.dirs=./lib/<specificOsFolder>" JRE argument. This should be removed.
The example SWT-AUT "Simple Adder" launches as usual again.
is closed
reassigned, cause changes from comment 2 have to be done first.
fixed with commit d8856b2b4f662a143584856879ad12930f1bb860
JRE Arguments are deleted
closed cause comment 7