Eclipse Community Forums: Jubula » AUT is shown under "Running AUTs" but won't start up

Home » Archived » Jubula » AUT is shown under "Running AUTs" but won't start up(Jubula doesn't show any error messages, works fine with previous version of AUT)

AUT is shown under "Running AUTs" but won't start up [message #1232142]

Thu, 16 January 2014 04:57

Eclipse User

Hey everyone!

I have updated my AUT and was trying to start my tests as usual but with this newest version of my AUT I experience a very weird error. When I want to start the AUT it appears under "Running AUTs" but won't show up.

I didn't change any configuration and just replaced the old jar with the new one as usual. The testing works fine with the old jar.

So far I tried many different things to make it work again:

Checked if I made any changes in the code of the AUT that affect the start-up
Rebuilt the AUT
Checked if I'm using the same JavaSE-Version to compile
Checked if I could start the jar manually (also from the console in Windows)
Set up a new configuration for the updated AUT:
- Added JRE-Executable path
- Added JRE-Arguments (-jar example.jar %1 %2 %3)
--> AUT starts up but won't show in Running AUTs so testing isn't working
--> In the "progress"-window it says "Starting AUT with ID..." but nothing happens

In the end I'm really not sure what causes the error. Whether it's a problem of Jubula (because the AUT runs perfectly on my system and also starts from cmd) or if it's the changes in the AUT that can cause this behavior (but I double checked the changes and can't find anything).

It's really important for me to find a solution for this because I can't release the newest version without the testing. So I would be really happy about any advice Smile

Re: AUT is shown under "Running AUTs" but won't start up [message #1232257 is a reply to message #1232142]

Thu, 16 January 2014 09:30

Eclipse User

Hi Lars,

Can you specify what type of AUT it is?
If it's RCP, have you carefully followed the steps to add the RCP accessor?

Regardless of the type, you could start the AUT using autrun to see the command line output when it's starting. That might help.

Best regards,
Alex

Re: AUT is shown under "Running AUTs" but won't start up [message #1232601 is a reply to message #1232257]

Fri, 17 January 2014 04:56

Eclipse User

Hey Alex,

it's an pure Java-SWT-App. In the user-manual it says under 3.7.2.6 "The autrun command cannot be used for HTML or pure SWT AUT's." Moreover it's not possible for me to use the autorun because I haven't installed an AUT agent and I'm not using the native Jubula app but the Eclipse-Plugin. Furthermore I don't have admin-right on the computer I use for testing.
So I can't check any command line outputs Confused

There's another thing I'm dealing with which could be the reason for my problem. During debugging in Eclipse the AUT needs like 10 minutes to start up (2 days ago everything worked alright). When I'm just running the jar (not in debug mode) the AUT starts up in 1 second.
So I thought maybe Jubula is starting the AUT with debug-arguments and that's the reason why it seems to be running but won't show up. Hoping this was the solution I started the AUT through Jubula and waited one night if the AUT's GUI would "start". But after 10 hours of running that was not the case.

Do you know if Jubula uses debug-arguments to start up the AUT?

[Updated on: Fri, 17 January 2014 05:06] by Moderator

Re: AUT is shown under "Running AUTs" but won't start up [message #1233757 is a reply to message #1232601]

Mon, 20 January 2014 07:11

Eclipse User

Hi,

ah, I assumed it was RCP. Sorry.
As far as I know, we don't start the AUT with debug arguments (unless you have entered them in the AUT configuration - check the advanced and expert views to be sure).
From what you say, it sounds like something may indeed have changed in the startup for the AUT.

Keep us posted.

Best regards,
Alex

Re: AUT is shown under "Running AUTs" but won't start up [message #1234613 is a reply to message #1233757]

Wed, 22 January 2014 06:25

Eclipse User

So I couldn't figure out what's the reason for my problem.
Here you can take a look at my simple config of the AUT (it works for the old version of the AUT).

In the But I found the Jubula logs and noticed that when I start the AUT (it is still not showing up) and hit the opject mapping mode and stop the AUT again I get some Errors in the client-log of Jubula.
Here it is(I don't know if there's any helpful information for you.)

2014-01-22 12:18:14.182 [Connection.ReaderThread:Socket[addr=localhost/127.0.0.1,port=60000,localport=56060]] ERROR o.e.j.communication.Communicator - answer is of wrong type
2014-01-22 12:18:14.329 [Worker-1] WARN  o.e.jubula.client.core.ClientTest - No default Object Mappings could be found for the AUT.
2014-01-22 12:18:14.335 [Worker-1] WARN  o.e.j.c.c.c.BaseConnection - send() called to an unconnected connection
2014-01-22 12:18:14.343 [Worker-1] ERROR o.e.j.c.c.c.AUTConnection - communication error while setting Resource Bundle
org.eclipse.jubula.client.core.communication.BaseConnection$NotConnectedException: This connection is not connected
	at org.eclipse.jubula.client.core.communication.BaseConnection.send(BaseConnection.java:129) ~[org.eclipse.jubula.client.core_2.1.1.201309020759.jar:na]
	at org.eclipse.jubula.client.core.communication.AUTConnection.sendResourceBundlesToAut(AUTConnection.java:259) [org.eclipse.jubula.client.core_2.1.1.201309020759.jar:na]
	at org.eclipse.jubula.client.core.communication.AUTConnection.connectToAut(AUTConnection.java:225) [org.eclipse.jubula.client.core_2.1.1.201309020759.jar:na]
	at org.eclipse.jubula.client.core.ClientTest.startObjectMapping(ClientTest.java:413) [org.eclipse.jubula.client.core_2.1.1.201309020759.jar:na]
	at org.eclipse.jubula.client.ui.rcp.handlers.StartObjectMappingModeHandler$StartObjectMappingModeJob.run(StartObjectMappingModeHandler.java:134) [org.eclipse.jubula.client.ui.rcp_2.1.1.201309020759.jar:na]
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) [org.eclipse.core.jobs_3.5.300.v20130429-1813.jar:na]
2014-01-22 12:18:14.346 [Worker-1] ERROR o.e.j.c.c.c.BaseConnection - request() called to an unconnected connection
2014-01-22 12:18:14.346 [Worker-1] ERROR o.e.j.c.c.c.AUTConnection - Error occurred while establishing connection to AUT.
org.eclipse.jubula.client.core.communication.BaseConnection$NotConnectedException: This connection is not connected
	at org.eclipse.jubula.client.core.communication.BaseConnection.request(BaseConnection.java:162) ~[org.eclipse.jubula.client.core_2.1.1.201309020759.jar:na]
	at org.eclipse.jubula.client.core.ClientTest.setAutKeyboardLayout(ClientTest.java:746) [org.eclipse.jubula.client.core_2.1.1.201309020759.jar:na]
	at org.eclipse.jubula.client.core.communication.AUTConnection.connectToAut(AUTConnection.java:227) ~[org.eclipse.jubula.client.core_2.1.1.201309020759.jar:na]
	at org.eclipse.jubula.client.core.ClientTest.startObjectMapping(ClientTest.java:413) [org.eclipse.jubula.client.core_2.1.1.201309020759.jar:na]
	at org.eclipse.jubula.client.ui.rcp.handlers.StartObjectMappingModeHandler$StartObjectMappingModeJob.run(StartObjectMappingModeHandler.java:134) [org.eclipse.jubula.client.ui.rcp_2.1.1.201309020759.jar:na]
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) [org.eclipse.core.jobs_3.5.300.v20130429-1813.jar:na]
2014-01-22 12:18:22.025 [Close Session Factory] ERROR o.e.j.c.core.persistence.Persistor - dispose of Persistor failed
org.eclipse.swt.SWTException: Device is disposed
	at org.eclipse.swt.SWT.error(SWT.java:4397) ~[org.eclipse.swt.win32.win32.x86_3.102.0.v20130605-1544.jar:na]
	at org.eclipse.swt.SWT.error(SWT.java:4312) ~[org.eclipse.swt.win32.win32.x86_3.102.0.v20130605-1544.jar:na]
	at org.eclipse.swt.SWT.error(SWT.java:4283) ~[org.eclipse.swt.win32.win32.x86_3.102.0.v20130605-1544.jar:na]
	at org.eclipse.swt.widgets.Display.error(Display.java:1258) ~[org.eclipse.swt.win32.win32.x86_3.102.0.v20130605-1544.jar:na]
	at org.eclipse.swt.widgets.Display.getThread(Display.java:2600) ~[org.eclipse.swt.win32.win32.x86_3.102.0.v20130605-1544.jar:na]
	at org.eclipse.jubula.client.ui.rcp.sourceprovider.AbstractJBSourceProvider.gdFireSourceChanged(AbstractJBSourceProvider.java:54) ~[na:na]
	at org.eclipse.jubula.client.ui.rcp.sourceprovider.ActiveProjectSourceProvider.fireSourceChanged(ActiveProjectSourceProvider.java:140) ~[na:na]
	at org.eclipse.jubula.client.ui.rcp.sourceprovider.ActiveProjectSourceProvider.reactOnDatabaseEvent(ActiveProjectSourceProvider.java:154) ~[na:na]
	at org.eclipse.jubula.client.core.utils.DatabaseStateDispatcher.notifyListener(DatabaseStateDispatcher.java:67) ~[org.eclipse.jubula.client.core_2.1.1.201309020759.jar:na]
	at org.eclipse.jubula.client.core.persistence.Persistor.dispose(Persistor.java:1203) ~[org.eclipse.jubula.client.core_2.1.1.201309020759.jar:na]
	at org.eclipse.jubula.client.core.persistence.Persistor$1.run(Persistor.java:96) [org.eclipse.jubula.client.core_2.1.1.201309020759.jar:na]

[Updated on: Wed, 22 January 2014 06:32] by Moderator

Re: AUT is shown under "Running AUTs" but won't start up [message #1235377 is a reply to message #1234613]

Fri, 24 January 2014 02:35

Eclipse User

Hi there,

I'm drawing a blank I'm afraid. I don't think I've ever seen this - where an AUT was marked as running but wasn't actually there.
You said it's a pure SWT application - are you using (since the new version) any specific frameworks with the application? maybe there's something there.

Best regards,
Alex

Re: AUT is shown under "Running AUTs" but won't start up [message #1243625 is a reply to message #1235377]

Tue, 11 February 2014 03:09

Eclipse User

Hey everyone,

so I finally figured out what caused my problem with Jubula.
In my AUT I needed some custom colors. So I declared them like the following example

Color red = new Color (display, 255, 0, 0);

Thinking I could use this colors like the "system colors" I wasn't disposing them. So every time I use a custom color I have to immediately dispose it and initialize it just before I need it. Otherwise it won't work with Jubula.

red = new Color (display, 255, 0, 0);
text.setForeground(red);
red.dispose();

I don't know why the AUT worked just fine when I executed it myself. But for some reason Jubula refuses to start the GUI of your AUT when you don't dispose your custom colors properly.

[Updated on: Tue, 11 February 2014 03:10] by Moderator

Re: AUT is shown under "Running AUTs" but won't start up [message #1243936 is a reply to message #1243625]

Tue, 11 February 2014 12:10

Eclipse User

Wow, that is new information to me! Thanks so much for providing the hint to help others. I'll forward your comment onto the team as an interesting specimen. If anyone mentions anything, I'll report back.

Thanks!
Alex

Previous Topic:	Export is not working with plugins installed in eclipse
Next Topic:	Jubula

Goto Forum:

-=] Back to Top [=-

Current Time: Wed Jul 23 05:01:27 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter