Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Archived » Jubula » Starting SWT AUT(Error when starting SWT Application as AUT)
icon5.gif  Starting SWT AUT [message #689868] Tue, 28 June 2011 14:14 Go to next message
Stephan is currently offline Stephan Friend
Messages: 4
Registered: June 2011
Junior Member
Hi
I'm using Jubula standalone 0.9.0.qualifier.
I created a new test project and configured an existing SWT application I developed as an AUT (specifically I configured it to usw swt toolkit and configured the exe path to a batch file that starts the app).
I started the AUT agent, connected to it and then wanted to start the AUT (no test cases etc yet).
However, after a couple of seconds a window pops up:
An error occurred.
Reason:
5009: Aut start failed

The client log shows:
2011-06-28 15:57:07.657 [Connection.ReaderThread:Socket[addr=localhost/127.0.0.1,port=60000,localport=3093]] ERROR o.e.j.c.c.c.StartAUTServerStateCommand - AUTServer could not start: Error while starting AUT!

Any ideas?

Thanks for what looks like a very promising test tool!

Stephan
P.S. I tried the same with the example swt adder and had no problems starting it.

Report message to a moderator

Re: Starting SWT AUT [message #690318 is a reply to message #689868] Wed, 29 June 2011 11:22 Go to previous messageGo to next message
Stephan is currently offline Stephan Friend
Messages: 4
Registered: June 2011
Junior Member
Is there anything I need to do, so that jubula (or the AUT agent?) can connect to my SWT application?
I read that for rcp apps a plugin is necessary (which one unzips). However, my app is not an rcp app.
Any logs I can enable to get to the bottom of this?

Stephan

Report message to a moderator

Re: Starting SWT AUT [message #690322 is a reply to message #690318] Wed, 29 June 2011 11:28 Go to previous messageGo to next message
Francois Genolini is currently offline Francois GenoliniFriend
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 11:32]

Report message to a moderator

Re: Starting SWT AUT [message #690958 is a reply to message #690322] Thu, 30 June 2011 13:18 Go to previous messageGo to next message
Stephan is currently offline Stephan Friend
Messages: 4
Registered: June 2011
Junior Member
Hi
The aut_agent logs are empty!
The client log contains:
2011-06-30 15:11:31.173 [main] WARN o.e.j.c.c.c.BaseConnection - send() called to an unconnected connection
2011-06-30 15:11:31.188 [main] ERROR o.e.jubula.client.core.ClientTest - org.eclipse.jubula.client.core.communication.BaseConnection$NotConnectedException: This connection is not connected
2011-06-30 15:11:45.611 [main] WARN o.e.j.c.c.c.BaseConnection - send() called to an unconnected connection
2011-06-30 15:11:45.611 [main] ERROR o.e.jubula.client.core.ClientTest - org.eclipse.jubula.client.core.communication.BaseConnection$NotConnectedException: This connection is not connected
2011-06-30 15:12:30.706 [Connection.ReaderThread:Socket[addr=localhost/127.0.0.1,port=60000,localport=1814]] ERROR o.e.j.c.c.c.StartAUTServerStateCommand - AUTServer could not start: Error while starting AUT!


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.

Report message to a moderator

Re: Starting SWT AUT [message #690977 is a reply to message #690958] Thu, 30 June 2011 13:49 Go to previous messageGo to next message
Francois Genolini is currently offline Francois GenoliniFriend
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 Wink

[Updated on: Thu, 30 June 2011 14:24]

Report message to a moderator

Re: Starting SWT AUT [message #691061 is a reply to message #690958] Thu, 30 June 2011 15:59 Go to previous messageGo to next message
Eclipse UserFriend
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

Report message to a moderator

Re: Starting SWT AUT [message #691389 is a reply to message #691061] Fri, 01 July 2011 11:06 Go to previous messageGo to next message
Stephan is currently offline Stephan Friend
Messages: 4
Registered: June 2011
Junior Member
Hi

Thanks for all the hints, but it looks like the settings are correct.
Here's a screen shot.
index.php/fa/3210/0/
I also tried specifying the jar itself instead of the batchfile, but same problem.

Maybe I can try to add some logging/debugging to the relevant source files,if you could point me in the right direction?

Stephan

Report message to a moderator

Re: Starting SWT AUT [message #691429 is a reply to message #691389] Fri, 01 July 2011 12:56 Go to previous messageGo to next message
Francois Genolini is currently offline Francois GenoliniFriend
Messages: 14
Registered: June 2011
Location: UK, Aberdeen
Junior Member
Divide and conquer Wink
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 12:57]

Report message to a moderator

Re: Starting SWT AUT [message #1009063 is a reply to message #689868] Thu, 14 February 2013 11:12 Go to previous messageGo to next message
Alexander Berger is currently offline Alexander BergerFriend
Messages: 13
Registered: January 2013
Junior Member
Hi,

my SWT AUT don't start with Jubula 1.3.0 standalone(5009: AUT start failed).
With cmd the JAR file starts and also with doublclick on the JAR file it starts.

I create the JAR file with eclipse Juno (Right click on the Project-> Export...-> Runnable JAR file-> Select "Package required libraries into generated JAR"-> Finish".

The AUT Agent log shows nothing.
The Client Agent log shows: "2013-02-14 12:05:44.192 [Connection.ReaderThread:Socket[addr=localhost/127.0.0.1,port=60000,localport=50948]] ERROR o.e.j.c.c.c.StartAUTServerStateCommand - AUTServer could not start: Error while starting AUT!"

In the AUT configuration I only have selected the JAR file.

Report message to a moderator

Re: Starting SWT AUT [message #1009431 is a reply to message #1009063] Fri, 15 February 2013 06:13 Go to previous messageGo to next message
Alexandra Schladebeck is currently offline Alexandra SchladebeckFriend
Messages: 1613
Registered: July 2009
Senior Member
Hi,

Aside from the rather excellent help above, the only things that come to mind are:
- are you 100% sure it is a pure SWT application, and not an Eclipse RCP application (sorry if this is a silly question, but the latter is more common than the former). If so, what version of Eclipse is it based on?
- bear in mind that the AUT config dialog should be a reflection of what you enter on the cmd. Anything (arguments etc) you enter there has to appear in the AUT config as well.

HTH,
Alex

Report message to a moderator

Re: Starting SWT AUT [message #1009529 is a reply to message #689868] Fri, 15 February 2013 09:28 Go to previous messageGo to next message
Alexander Berger is currently offline Alexander BergerFriend
Messages: 13
Registered: January 2013
Junior Member
Hi,

-yes it is a pure SWT application.(eclipse Juno32bit
Version: Juno Service Release 1 & Windows 7 64bit)
-in the AUT configuration I add the directory from the JAR file.
And my cmd command is "java -jar C:\Users\berger\Desktop\NatTable.jar", the JAR file runs with the cmd command.

Report message to a moderator

Re: Starting SWT AUT [message #1012764 is a reply to message #1009529] Fri, 22 February 2013 07:45 Go to previous messageGo to next message
Alexandra Schladebeck is currently offline Alexandra SchladebeckFriend
Messages: 1613
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

Report message to a moderator

Re: Starting SWT AUT [message #1505246 is a reply to message #689868] Tue, 09 December 2014 23:48 Go to previous messageGo to next message
a goettl is currently offline a goettlFriend
Messages: 17
Registered: December 2014
Junior Member
I have encountered the same issue. Was a resolution ever found? My application also starts correctly outside of Jubula, but when I startAUT, the JVM terminates with exit code 25.

Report message to a moderator

Re: Starting SWT AUT [message #1505670 is a reply to message #1505246] Wed, 10 December 2014 08:08 Go to previous messageGo to next message
Alexandra Schladebeck is currently offline Alexandra SchladebeckFriend
Messages: 1613
Registered: July 2009
Senior Member
Hi Andy,

Is your AUT definitely an SWT AUT (I know it sounds like a silly question, but many people say "SWT" and mean "RCP" Wink ). What is in the AUT Agent Log? What platform are you on, what version of Java are you using?

Thanks for the information,

Alex

Report message to a moderator

Re: Starting SWT AUT [message #1506125 is a reply to message #1505246] Wed, 10 December 2014 15:54 Go to previous messageGo to next message
a goettl is currently offline a goettlFriend
Messages: 17
Registered: December 2014
Junior Member
Resolution found. I am using Hudson jobs to build and deploy the AUT. A different user owned the file permissions for the workspace/.metadata in the base/working directory than the user running the test. Either need to have the same user, or open file permissions in the working directory.

Report message to a moderator

Re: Starting SWT AUT [message #1507118 is a reply to message #1506125] Thu, 11 December 2014 10:29 Go to previous messageGo to next message
Alexandra Schladebeck is currently offline Alexandra SchladebeckFriend
Messages: 1613
Registered: July 2009
Senior Member
Thanks for posting the answer! Smile

Report message to a moderator

Re: Starting SWT AUT [message #1699002 is a reply to message #689868] Fri, 19 June 2015 12:10 Go to previous messageGo to next message
Nick S is currently offline Nick SFriend
Messages: 4
Registered: March 2014
Junior Member
I have what seems to be exactly this problem (persistent 5009: AUT start failed), using the Jubula Function Testing plugin 2.3.0.201406030848 downloaded via the eclipse marketplace. (I have Eclipse Juno, Service Release 2 build ID 3.0.201406030848, and am running on Ubuntu Precise.) I am using the embedded AUT.

There appears to be no information in the logs, the help->client log and help->aut log menu items do nothing, and in ~/.jubula/logs I find only old log files for aut_agent.log and client.log (with errors from my previous efforts, no doubt)

However, checking the process information for eclipse, I see it is writing in ~/.xsession-errors, and there's a clue there (see below). Essentially it looks like there's an exception killing the AUT, "NoClassDefFoundError: org/apache/log4j/Level". Note this is not a ClassNotFoundException. The SLF4J message is allegedly just a warning, I am not sure if it is relevant.

Elsewhere in the .xsession-errors file, I also see the error (also below) "No appenders could be found for logger (org.eclipse.jubula.client.core.ClientTestImpl)."

Being bold, Iguessed the SLG4J message *is* related, so I moved the older jar mentioned (org.slf4j.impl.log4j12_1.7.2.v20131105-2200.jar) away, and restarted eclipse. Now the AUT fails, but again the error appears in .xsession-errors, and for a different error, one created by my application. Now that error is one I know how to fix, and the next time I run the AUT, the application starts!

So, the important thing seems to be to remember to look in .xsession-errors (or an equivalent), as the Log4J initialisation can fail. In my case, SLF4J seems to have two bindings, and the wrong one is chosen. Maybe this will help someone else.

AUT:SLF4J: Class path contains multiple SLF4J bindings.
AUT:SLF4J: Found binding in [jar:file:/home/nick/i/eclipse/plugins/org.slf4j.impl.log4j12_1.7.2.v20131105-2200.jar!/org/slf4j/impl/StaticLoggerBinder.class]
AUT:SLF4J: Found binding in [jar:file:/home/nick/i/eclipse/plugins/ch.qos.logback.slf4j_1.0.7.v20121108-1250.jar!/org/slf4j/impl/StaticLoggerBinder.class]
AUT:SLF4J: See http //www.slf4j.org/codes.html#multiple_bindings for an explanation.
AUT:Failed to instantiate SLF4J LoggerFactory
AUT:Reported exception:
AUT:java.lang.NoClassDefFoundError: org/apache/log4j/Level
AUT:	at org.slf4j.LoggerFactory.bind(LoggerFactory.java:128)
AUT:	at org.slf4j.LoggerFactory.performInitialization(LoggerFactory.java:107)
AUT:	at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:295)
AUT:	at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:269)
AUT:	at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:281)
AUT:	at org.eclipse.jubula.rc.common.AUTServer.<clinit>(AUTServer.java:78)
AUT:	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
AUT:	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
AUT:	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
AUT:	at java.lang.reflect.Method.invoke(Method.java:606)
AUT:	at org.eclipse.jubula.rc.common.AutServerLauncher.main(AutServerLauncher.java:96)
AUT:Caused by: java.lang.ClassNotFoundExceptioAUT:SLF4J: Class path contains multiple SLF4J bindings.
AUT:SLF4J: Found binding in [jar:file:/home/nick/i/eclipse/plugins/org.slf4j.impl.log4j12_1.7.2.v20131105-2200.jar!/org/slf4j/impl/StaticLoggerBinder.class]
AUT:SLF4J: Found binding in [jar:file:/home/nick/i/eclipse/plugins/ch.qos.logback.slf4j_1.0.7.v20121108-1250.jar!/org/slf4j/impl/StaticLoggerBinder.class]
AUT:SLF4J: See http //www.slf4j.org/codes.html#multiple_bindings for an explanation.
AUT:Failed to instantiate SLF4J LoggerFactory
AUT:Reported exception:
AUT:java.lang.NoClassDefFoundError: org/apache/log4j/Level
AUT:	at org.slf4j.LoggerFactory.bind(LoggerFactory.java:128)
AUT:	at org.slf4j.LoggerFactory.performInitialization(LoggerFactory.java:107)
AUT:	at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:295)
AUT:	at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:269)
AUT:	at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:281)
AUT:	at org.eclipse.jubula.rc.common.AUTServer.<clinit>(AUTServer.java:78)
AUT:	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
AUT:	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
AUT:	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
AUT:	at java.lang.reflect.Method.invoke(Method.java:606)
AUT:	at org.eclipse.jubula.rc.common.AutServerLauncher.main(AutServerLauncher.java:96)
AUT:Caused by: java.lang.ClassNotFoundException: org.apache.log4j.Level
AUT:	at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
AUT:	at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
AUT:	at java.security.AccessController.doPrivileged(Native Method)
AUT:	at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
AUT:	at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
AUT:	at org.eclipse.jubula.rc.common.AutServerLauncher$UrlDefaultClassLoader.loadClass(AutServerLauncher.java:228)
AUT:	at org.eclipse.jubula.rc.common.AutServerLauncher$UrlDefaultClassLoader.loadClass(AutServerLauncher.java:246)
AUT:	... 11 more
AUT:Exception in thread "main" java.lang.NoClassDefFoundError: org/apache/log4j/Level
AUT:	at org.slf4j.LoggerFactory.bind(LoggerFactory.java:128)
AUT:	at org.slf4j.LoggerFactory.performInitialization(LoggerFactory.java:107)
AUT:	at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:295)
AUT:	at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:269)
AUT:	at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:281)
AUT:	at org.eclipse.jubula.rc.common.AUTServer.<clinit>(AUTServer.java:78)
AUT:	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
AUT:	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
AUT:	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
AUT:	at java.lang.reflect.Method.invoke(Method.java:606)
AUT:	at org.eclipse.jubula.rc.common.AutServerLauncher.main(AutServerLauncher.java:96)
AUT:Caused by: java.lang.ClassNotFoundException: org.apache.log4j.Level
AUT:	at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
AUT:	at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
AUT:	at java.security.AccessController.doPrivileged(Native Method)
AUT:	at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
AUT:	at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
AUT:	at org.eclipse.jubula.rc.common.AutServerLauncher$UrlDefaultClassLoader.loadClass(AutServerLauncher.java:228)
AUT:	at org.eclipse.jubula.rc.common.AutServerLauncher$UrlDefaultClassLoader.loadClass(AutServerLauncher.java:246)
AUT:	... 11 more
plasma-desktop(2590)/plasma StatusNotifierItemSource::refreshCallback: DBusMenu disabled for this application 

(process:2590): libindicate-WARNING **: Unable to get property data: GDBus.Error:com.canonical.indicate.NO_SUCH_PROPERTY: Indicator 146 has no property named 'icon'

(process:2590): libindicate-WARNING **: Unable to get property data: GDBus.Error:com.canonical.indicate.NO_SUCH_PROPERTY: Indicator 146 has no property named 'time'

(process:2590): libindicate-WARNING **: Unable to get property data: GDBus.Error:com.canonical.indicate.NO_SUCH_PROPERTY: Indicator 146 has no property named 'draw-attention'
plasma-desktop(2590)/plasma StatusNotifierItemSource::refreshCallback: DBusMenu disabled for this application 
plasma-desktop(2590)/plasma StatusNotifierItemSource::refreshCallback: DBusMenu disabled for this application 
plasma-desktop(2590)/plasma StatusNotifierItemSource::refreshCallback: DBusMenu disabled for this application 

(process:2590): libindicate-WARNING **: Unable to get property data: GDBus.Error:com.canonical.indicate.NO_SUCH_PROPERTY: Indicator 147 has no property named 'icon'

(process:2590): libindicate-WARNING **: Unable to get property data: GDBus.Error:com.canonical.indicate.NO_SUCH_PROPERTY: Indicator 147 has no property named 'time'

(process:2590): libindicate-WARNING **: Unable to get property data: GDBus.Error:com.canonical.indicate.NO_SUCH_PROPERTY: Indicator 147 has no property named 'draw-attention'
n: org.apache.log4j.Level
AUT:	at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
AUT:	at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
AUT:	at java.security.AccessController.doPrivileged(Native Method)
AUT:	at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
AUT:	at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
AUT:	at org.eclipse.jubula.rc.common.AutServerLauncher$UrlDefaultClassLoader.loadClass(AutServerLauncher.java:228)
AUT:	at org.eclipse.jubula.rc.common.AutServerLauncher$UrlDefaultClassLoader.loadClass(AutServerLauncher.java:246)
AUT:	... 11 more
AUT:Exception in thread "main" java.lang.NoClassDefFoundError: org/apache/log4j/Level
AUT:	at org.slf4j.LoggerFactory.bind(LoggerFactory.java:128)
AUT:	at org.slf4j.LoggerFactory.performInitialization(LoggerFactory.java:107)
AUT:	at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:295)
AUT:	at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:269)
AUT:	at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:281)
AUT:	at org.eclipse.jubula.rc.common.AUTServer.<clinit>(AUTServer.java:78)
AUT:	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
AUT:	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
AUT:	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
AUT:	at java.lang.reflect.Method.invoke(Method.java:606)
AUT:	at org.eclipse.jubula.rc.common.AutServerLauncher.main(AutServerLauncher.java:96)
AUT:Caused by: java.lang.ClassNotFoundException: org.apache.log4j.Level
AUT:	at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
AUT:	at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
AUT:	at java.security.AccessController.doPrivileged(Native Method)
AUT:	at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
AUT:	at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
AUT:	at org.eclipse.jubula.rc.common.AutServerLauncher$UrlDefaultClassLoader.loadClass(AutServerLauncher.java:228)
AUT:	at org.eclipse.jubula.rc.common.AutServerLauncher$UrlDefaultClassLoader.loadClass(AutServerLauncher.java:246)
AUT:	... 11 more
plasma-desktop(2590)/plasma StatusNotifierItemSource::refreshCallback: DBusMenu disabled for this application 

(process:2590): libindicate-WARNING **: Unable to get property data: GDBus.Error:com.canonical.indicate.NO_SUCH_PROPERTY: Indicator 146 has no property named 'icon'

(process:2590): libindicate-WARNING **: Unable to get property data: GDBus.Error:com.canonical.indicate.NO_SUCH_PROPERTY: Indicator 146 has no property named 'time'

(process:2590): libindicate-WARNING **: Unable to get property data: GDBus.Error:com.canonical.indicate.NO_SUCH_PROPERTY: Indicator 146 has no property named 'draw-attention'
plasma-desktop(2590)/plasma StatusNotifierItemSource::refreshCallback: DBusMenu disabled for this application 
plasma-desktop(2590)/plasma StatusNotifierItemSource::refreshCallback: DBusMenu disabled for this application 
plasma-desktop(2590)/plasma StatusNotifierItemSource::refreshCallback: DBusMenu disabled for this application 

(process:2590): libindicate-WARNING **: Unable to get property data: GDBus.Error:com.canonical.indicate.NO_SUCH_PROPERTY: Indicator 147 has no property named 'icon'

(process:2590): libindicate-WARNING **: Unable to get property data: GDBus.Error:com.canonical.indicate.NO_SUCH_PROPERTY: Indicator 147 has no property named 'time'

(process:2590): libindicate-WARNING **: Unable to get property data: GDBus.Error:com.canonical.indicate.NO_SUCH_PROPERTY: Indicator 147 has no property named 'draw-attention'




SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [bundleresource://2381.fwk295932193:1/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [bundleresource://2381.fwk295932193:2/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http //www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
log4j:WARN No appenders could be found for logger (org.eclipse.jubula.client.core.ClientTestImpl).
log4j:WARN Please initialize the log4j system properly.

Report message to a moderator

Re: Starting SWT AUT [message #1699110 is a reply to message #1699002] Sun, 21 June 2015 11:34 Go to previous messageGo to next message
Alexandra Schladebeck is currently offline Alexandra SchladebeckFriend
Messages: 1613
Registered: July 2009
Senior Member
Thanks for the detailed post!

Report message to a moderator

Re: Starting SWT AUT [message #1795157 is a reply to message #689868] Mon, 17 September 2018 11:03 Go to previous messageGo to next message
Meghana Iyer is currently offline Meghana IyerFriend
Messages: 6
Registered: September 2018
Junior Member
Facing the same issue on CentOS:

AUT is an SWT application

2018-09-17 15:53:29.830 [Worker-8] WARN o.e.j.client.core.ClientTestImpl - connecting the AUT Agent failed
2018-09-17 15:53:35.470 [Worker-15] WARN o.e.j.client.core.ClientTestImpl - connecting the AUT Agent failed
2018-09-17 15:55:12.404 [Connection.ReaderThread:Socket[addr=localhost/127.0.0.1,port=60000,localport=59916]] ERROR o.e.j.c.i.c.StartAUTServerStateCommand - AUTServer could not start: Unknown AUTServer exit code: 31.
Picked up _JAVA_OPTIONS: "-javaagent:/home/meghana/Desktop/jubula_8.6.0.262/ite/plugins/org.eclipse.jubula.rc.common.agent_6.0.0.201802230740.jar"
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.eclipse.jubula.rc.common.AutServerLauncher.main(AutServerLauncher.java:96)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.eclipse.jubula.rc.common.agent.RCAgent.premain(RCAgent.java:103)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at sun.instrument.InstrumentationImpl.loadClassAndStartAgent(InstrumentationImpl.java:386)
at sun.instrument.InstrumentationImpl.loadClassAndCallPremain(InstrumentationImpl.java:401)
Caused by: java.lang.NoClassDefFoundError: org/eclipse/swt/widgets/Listener
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:763)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:467)

Report message to a moderator

Re: Starting SWT AUT [message #1795399 is a reply to message #1795157] Fri, 21 September 2018 11:15 Go to previous messageGo to next message
Marvin Mueller is currently offline Marvin MuellerFriend
Messages: 255
Registered: March 2012
Senior Member
Hello Meghana Iyer,
is the shell file working without Jubula?
is the Application which should be tested the first java application in the shell script?

Are you sure your Application is SWT. I assume this because a basic SWT listener is not found. Maybe it is an RCP application with SWT in it or something similar.

best regards
Marvin

Report message to a moderator

Re: Starting SWT AUT [message #1795491 is a reply to message #1795399] Mon, 24 September 2018 09:47 Go to previous messageGo to next message
Meghana Iyer is currently offline Meghana IyerFriend
Messages: 6
Registered: September 2018
Junior Member
Thanks Marvin,
Yes the shell file works fine without jubula
Will need more information about the application from the development team here.

Report message to a moderator

Re: Starting SWT AUT [message #1795492 is a reply to message #1795399] Mon, 24 September 2018 09:47 Go to previous messageGo to next message
Meghana Iyer is currently offline Meghana IyerFriend
Messages: 6
Registered: September 2018
Junior Member
Thanks Marvin,
Yes the shell file works fine without jubula
Will need more information about the application from the development team here.

Report message to a moderator

Re: Starting SWT AUT [message #1795493 is a reply to message #1795399] Mon, 24 September 2018 09:47 Go to previous message
Meghana Iyer is currently offline Meghana IyerFriend
Messages: 6
Registered: September 2018
Junior Member
Thanks Marvin,
Yes the shell file works fine without jubula
Will need more information about the application from the development team here.

Report message to a moderator

Previous Topic:Unable to start AUT which is a JNLP successfully
Next Topic:Unable to start AUT which is a JNLP successfully
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ]

Current Time: Thu Apr 18 02:30:16 GMT 2024

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

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

Back to the top

Sign up to our Newsletter

A fresh new issue delivered monthly