|
|
| Re: Starting SWT AUT [message #690322 is a reply to message #690318] |
Wed, 29 June 2011 07:28   |
Francois Genolini Messages: 14 Registered: June 2011 Location: UK, Aberdeen |
Junior Member |
|
|
You say that you have successfully managed to start at least one of the Jubula example AUTs. Because they work, then its your app that is not starting.
Does your app start from the command line?
Have you specified the JRE as well as your app?
The logs are in the user's home directory under .jubula/logs/aut_agent_0.log
[Updated on: Wed, 29 June 2011 07:32] Report message to a moderator
|
|
|
|
| Re: Starting SWT AUT [message #690977 is a reply to message #690958] |
Thu, 30 June 2011 09:49   |
Francois Genolini Messages: 14 Registered: June 2011 Location: UK, Aberdeen |
Junior Member |
|
|
I have tried to do something similar to what you suggest, but mine works.
The difference seems to be that I have a few more lines at the start of my batch file:
D:
CD \Folder\Where\JAR\File\Is
"C:\Program Files\Java\jdk1.6.0_26\bin\javaw.exe" -jar name_of_jar_file.jar %1 %2 %3
As long as all the paths are known, this should work.
I have not managed to get the same error as you have, but I have others.
For example if deliberately specify the wrong jar file (typo, jar file not in class path because batch file started from another drive and folder...) I get the following error message in the client log:
[Connection.ReaderThread:Socket[addr=/myIP,port=60000,localport=63748]] ERROR o.e.j.c.c.c.StartAUTServerStateCommand - AUTServer could not start: invalid arguments
Also if I deliberately make my Java application fail and return error code -1 using System.exit(-1), I get an error message in the standalone ITE saying:
5009: AUT start failed
Establishing connection to AUT failed.
Please check the AUT configuration.
I also get an error message in the Client log:
[Connection.ReaderThread:Socket[addr=/myIP,port=60000,localport=64068]] ERROR o.e.j.c.c.c.StartAUTServerStateCommand - AUTServer could not start: unknown AUTServer exit code: '-1'
This all seems to work as designed and be rather good at error reporting 
[Updated on: Thu, 30 June 2011 10:24] Report message to a moderator
|
|
|
| Re: Starting SWT AUT [message #691061 is a reply to message #690958] |
Thu, 30 June 2011 11:59   |
|
Originally posted by:
On 2011-06-30 15:18:16 +0200, Stephan said:
> The batch file I am trying to start as AUT (and I can start it
> manually) looks like this:
>
> "C:\Program Files\Java\jdk1.6.0_19\jre\bin\javaw" -jar pedit.jar %1 %2 %3
> The parameters are optional.
Francois might be on to something. Did you set the the "AUT
Base/Working Directory" in the AUT configuration? jar files and all
other elements with relative path names on the classpath are looked up
using this directory as its base. The default for this directory is the
installation directory of the AUTAgent.
- Achim
|
|
|
|
| Re: Starting SWT AUT [message #691429 is a reply to message #691389] |
Fri, 01 July 2011 08:56   |
Francois Genolini Messages: 14 Registered: June 2011 Location: UK, Aberdeen |
Junior Member |
|
|
Divide and conquer 
First just call your Jar without a batch file (specify JRE, JAR and class path).
If this works, then your software is OK, but there is somehow an issue with batch files.
If this does not work just add Java Logging API calls (and save to simple text file).
Call System.exit(-1) as the first instruction in your main.
You should get the same error message that I had earlier:
AUTServer could not start: unknown AUTServer exit code: '-1'
If you do not, then your JRE has an issue (your code is not even run), or some of your static initialisers do something really bad.
Try the latest JDK (1.6.0_26).
If you do have the expected error, then add info (or severe) Java Logging API messages gradually to your program.
[Updated on: Fri, 01 July 2011 08:57] Report message to a moderator
|
|
|
|
|
|
| Re: Starting SWT AUT [message #1012764 is a reply to message #1009529] |
Fri, 22 February 2013 02:45  |
Alexandra Schladebeck Messages: 736 Registered: July 2009 |
Senior Member |
|
|
Hi,
I'm afraid I'm a bit stumped then. Unless the jar file is pointing to files that can't be reached from your installation, then I don't know what could be causing it. At this point, the only further thing I can suggest is that our support team could take a look at your application and its start mechanism - that would involve a support package. If you want more information, then send a mail to sales at bredex dot de.
Best regards,
Alex
|
|
|
Powered by
FUDForum. Page generated in 0.02002 seconds