Eclipse Community Forums: Jubula » testexec from Windows connect to linux AUT failed at the end

Home » Archived » Jubula » testexec from Windows connect to linux AUT failed at the end (AUT on Linux, Use testexec command on windows connect to Aut failed.)

Show: Today's Messages :: Show Polls :: Message Navigator

testexec from Windows connect to linux AUT failed at the end [message #1001197]

Wed, 16 January 2013 08:33

posia han

Messages: 43
Registered: December 2012

Member

Hi,

The version of jubula is standalone 1.3.0 .I start autagent on Linux ,and connect the AUT of Linux successfully at the Jubula LTE from windows machine, but when i used testexec command, the AUT started uncompletely, can you help me?

Errror message in the Client.log:
2013-01-17 18:25:59.078 [main] ERROR o.e.jubula.tools.i18n.CompSystemI18n - Cannot find I18N-key in resource bundles: newTab
java.util.MissingResourceException: No entry found for key: newTab
at org.eclipse.jubula.tools.i18n.CompSystemI18n.getStringInternal(CompSystemI18n.java:128) ~[org.eclipse.jubula.tools_1.3.0.201210161256.jar:na]
at org.eclipse.jubula.tools.i18n.CompSystemI18n.getString(CompSystemI18n.java:80) ~[org.eclipse.jubula.tools_1.3.0.201210161256.jar:na]
at org.eclipse.jubula.client.core.utils.StringHelper.initMap(StringHelper.java:154) [org.eclipse.jubula.client.core_1.3.0.201210161256.jar:na]
at org.eclipse.jubula.client.core.utils.StringHelper.<init>(StringHelper.java:56) [org.eclipse.jubula.client.core_1.3.0.201210161256.jar:na]
at org.eclipse.jubula.client.core.utils.StringHelper.getInstance(StringHelper.java:85) [org.eclipse.jubula.client.core_1.3.0.201210161256.jar:na]
at org.eclipse.jubula.client.core.businessprocess.ComponentNamesBP.initDefaultNames(ComponentNamesBP.java:743) [org.eclipse.jubula.client.core_1.3.0.201210161256.jar:na]
at org.eclipse.jubula.client.core.businessprocess.ComponentNamesBP.<init>(ComponentNamesBP.java:158) [org.eclipse.jubula.client.core_1.3.0.201210161256.jar:na]
at org.eclipse.jubula.client.core.businessprocess.ComponentNamesBP.getInstance(ComponentNamesBP.java:167) [org.eclipse.jubula.client.core_1.3.0.201210161256.jar:na]
at org.eclipse.jubula.client.core.persistence.ProjectPM.loadProjectInROSession(ProjectPM.java:507) [org.eclipse.jubula.client.core_1.3.0.201210161256.jar:na]
at org.eclipse.jubula.app.cmd.batch.ExecutionController.loadProject(ExecutionController.java:776) [org.eclipse.jubula.app.cmd_1.3.0.201210161256.jar:na]
at org.eclipse.jubula.app.cmd.batch.ExecutionController.prepareExecution(ExecutionController.java:573) [org.eclipse.jubula.app.cmd_1.3.0.201210161256.jar:na]
at org.eclipse.jubula.app.cmd.batch.ExecutionController.executeJob(ExecutionController.java:410) [org.eclipse.jubula.app.cmd_1.3.0.201210161256.jar:na]
at org.eclipse.jubula.app.cmd.Client.doRun(Client.java:81) [org.eclipse.jubula.app.cmd_1.3.0.201210161256.jar:na]
at org.eclipse.jubula.client.cmd.AbstractCmdlineClient.run(AbstractCmdlineClient.java:407) [org.eclipse.jubula.client.cmd_1.3.0.201210161256.jar:na]
at org.eclipse.jubula.client.cmd.AbstractLauncher.start(AbstractLauncher.java:26) [org.eclipse.jubula.client.cmd_1.3.0.201210161256.jar:na]
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) [org.eclipse.equinox.app_1.3.100.v20110321.jar:na]
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) [org.eclipse.osgi_3.7.2.v20120110-1415.jar:na]
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) [org.eclipse.osgi_3.7.2.v20120110-1415.jar:na]
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344) [org.eclipse.osgi_3.7.2.v20120110-1415.jar:na]
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) [org.eclipse.osgi_3.7.2.v20120110-1415.jar:na]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.6.0_33]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) ~[na:1.6.0_33]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) ~[na:1.6.0_33]
at java.lang.reflect.Method.invoke(Method.java:597) ~[na:1.6.0_33]
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) [org.eclipse.equinox.launcher_1.2.0.v20110502.jar:na]
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) [org.eclipse.equinox.launcher_1.2.0.v20110502.jar:na]
at org.eclipse.equinox.launcher.Main.run(Main.java:1410) [org.eclipse.equinox.launcher_1.2.0.v20110502.jar:na]
at org.eclipse.equinox.launcher.Main.main(Main.java:1386) [org.eclipse.equinox.launcher_1.2.0.v20110502.jar:na]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.6.0_33]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) ~[na:1.6.0_33]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) ~[na:1.6.0_33]
at java.lang.reflect.Method.invoke(Method.java:597) ~[na:1.6.0_33]
at com.exe4j.runtime.LauncherEngine.launch(Unknown Source) [i4jruntime.jar:na]
at com.exe4j.runtime.WinLauncher.main(Unknown Source) [i4jruntime.jar:na]
at com.install4j.runtime.launcher.WinLauncher.main(Unknown Source) [i4jruntime.jar:na]
2013-01-17 18:26:25.468 [Worker-0] ERROR o.e.j.c.c.c.AUTConnection - Connection to AUT could not be established.
2013-01-17 18:26:25.468 [Worker-0] ERROR o.e.j.c.cmd.AbstractCmdlineClient - An error ocurred: Could not connect to AUT

[Updated on: Fri, 18 January 2013 00:58]

Report message to a moderator

Re: testexec from Windows connect to linux AUT failed at the end [message #1002197 is a reply to message #1001197]

Fri, 18 January 2013 06:43

Alexandra Schladebeck

Messages: 1613
Registered: July 2009

Senior Member

The last two lines of the log file are the relevant ones here. The connection to the AUT could not be made. Some reasons off the top of my head:

- There is a problem with the AUT configuration being used
- The AUT is RCP and the splash screen to enter the workspace is visible (the workspace must be configured in the AUT configuration. See this thread for more details)
- There is a firewall / network problem, as described in this thread.

Hope that helps!
Alex

Report message to a moderator

Re: testexec from Windows connect to linux AUT failed at the end [message #1002208 is a reply to message #1002197]

Fri, 18 January 2013 07:12

posia han

Messages: 43
Registered: December 2012

Member

Hi ALEX,
Follow what you suggest,I tried testexec command on AUT local machine,but The same problem comes again. At this time,I also added -data parameter into .xml file.

1.The content of .xml file:
<configuration>
<project>NetNumen</project>
<version>1.0</version>
<autconfig>P2B4SP002Setup@CGSL</autconfig>
<dbscheme>Netnumen</dbscheme>
<dbuser>system</dbuser>
<dbpw>abc123</dbpw>
<server>192.168.0.83</server>
<port>60000</port>
<language>zh_CN</language>
<testsuite>SP002SetupSuit</testsuite>
<data>/tools/jubula/jubula/workspace</data>
<datadir>/datafile/testdata</datadir>
<resultdir>/datafile/testdata</resultdir>
</configuration>

2.The error log:
2013-01-18 16:14:09.150 [main] ERROR o.e.jubula.tools.i18n.CompSystemI18n - Cannot find I18N-key in resource bundles: previous
java.util.MissingResourceException: No entry found for key: previous
at org.eclipse.jubula.tools.i18n.CompSystemI18n.getStringInternal(CompSystemI18n.java:128) ~[org.eclipse.jubula.tools_1.3.0.201210161256.jar:na]
at org.eclipse.jubula.tools.i18n.CompSystemI18n.getString(CompSystemI18n.java:80) ~[org.eclipse.jubula.tools_1.3.0.201210161256.jar:na]
at org.eclipse.jubula.client.core.utils.StringHelper.initMap(StringHelper.java:154) [org.eclipse.jubula.client.core_1.3.0.201210161256.jar:na]
at org.eclipse.jubula.client.core.utils.StringHelper.<init>(StringHelper.java:56) [org.eclipse.jubula.client.core_1.3.0.201210161256.jar:na]
at org.eclipse.jubula.client.core.utils.StringHelper.getInstance(StringHelper.java:85) [org.eclipse.jubula.client.core_1.3.0.201210161256.jar:na]
at org.eclipse.jubula.client.core.businessprocess.ComponentNamesBP.initDefaultNames(ComponentNamesBP.java:743) [org.eclipse.jubula.client.core_1.3.0.201210161256.jar:na]
at org.eclipse.jubula.client.core.businessprocess.ComponentNamesBP.<init>(ComponentNamesBP.java:158) [org.eclipse.jubula.client.core_1.3.0.201210161256.jar:na]
at org.eclipse.jubula.client.core.businessprocess.ComponentNamesBP.getInstance(ComponentNamesBP.java:167) [org.eclipse.jubula.client.core_1.3.0.201210161256.jar:na]
at org.eclipse.jubula.client.core.persistence.ProjectPM.loadProjectInROSession(ProjectPM.java:507) [org.eclipse.jubula.client.core_1.3.0.201210161256.jar:na]
at org.eclipse.jubula.app.cmd.batch.ExecutionController.loadProject(ExecutionController.java:776) [org.eclipse.jubula.app.cmd_1.3.0.201210161256.jar:na]
at org.eclipse.jubula.app.cmd.batch.ExecutionController.prepareExecution(ExecutionController.java:573) [org.eclipse.jubula.app.cmd_1.3.0.201210161256.jar:na]
at org.eclipse.jubula.app.cmd.batch.ExecutionController.executeJob(ExecutionController.java:410) [org.eclipse.jubula.app.cmd_1.3.0.201210161256.jar:na]
at org.eclipse.jubula.app.cmd.Client.doRun(Client.java:81) [org.eclipse.jubula.app.cmd_1.3.0.201210161256.jar:na]
at org.eclipse.jubula.client.cmd.AbstractCmdlineClient.run(AbstractCmdlineClient.java:407) [org.eclipse.jubula.client.cmd_1.3.0.201210161256.jar:na]
at org.eclipse.jubula.client.cmd.AbstractLauncher.start(AbstractLauncher.java:26) [org.eclipse.jubula.client.cmd_1.3.0.201210161256.jar:na]
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) [org.eclipse.equinox.app_1.3.100.v20110321.jar:na]
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) [org.eclipse.osgi_3.7.2.v20120110-1415.jar:na]
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) [org.eclipse.osgi_3.7.2.v20120110-1415.jar:na]
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344) [org.eclipse.osgi_3.7.2.v20120110-1415.jar:na]
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) [org.eclipse.osgi_3.7.2.v20120110-1415.jar:na]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.6.0_33]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) ~[na:1.6.0_33]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) ~[na:1.6.0_33]
at java.lang.reflect.Method.invoke(Method.java:597) ~[na:1.6.0_33]
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) [org.eclipse.equinox.launcher_1.2.0.v20110502.jar:na]
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) [org.eclipse.equinox.launcher_1.2.0.v20110502.jar:na]
at org.eclipse.equinox.launcher.Main.run(Main.java:1410) [org.eclipse.equinox.launcher_1.2.0.v20110502.jar:na]
at org.eclipse.equinox.launcher.Main.main(Main.java:1386) [org.eclipse.equinox.launcher_1.2.0.v20110502.jar:na]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.6.0_33]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) ~[na:1.6.0_33]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) ~[na:1.6.0_33]
at java.lang.reflect.Method.invoke(Method.java:597) ~[na:1.6.0_33]
at com.exe4j.runtime.LauncherEngine.launch(Unknown Source) [i4jruntime.jar:na]
at com.install4j.runtime.launcher.Launcher.main(Unknown Source) [i4jruntime.jar:na]
2013-01-18 16:14:35.590 [Worker-0] ERROR o.e.j.c.c.c.AUTConnection - Connection to AUT could not be established.
2013-01-18 16:14:35.605 [Worker-0] ERROR o.e.j.c.cmd.AbstractCmdlineClient - An error ocurred: Could not connect to AUT:test

Attachment: swing.bmp
(Size: 942.77KB, Downloaded 244 times)

[Updated on: Fri, 18 January 2013 08:20]

Report message to a moderator

Re: testexec from Windows connect to linux AUT failed at the end [message #1003346 is a reply to message #1002208]

Mon, 21 January 2013 02:22

posia han

Messages: 43
Registered: December 2012

Member

hello again,
Is there something wrong with my configuration .xml file?

The attachment is the AUT configuration of the ITE.And it works well.

Attachment: AUT Configuration.bmp
(Size: 1.15MB, Downloaded 257 times)

[Updated on: Mon, 21 January 2013 05:47]

Report message to a moderator

Re: testexec from Windows connect to linux AUT failed at the end [message #1003778 is a reply to message #1002197]

Tue, 22 January 2013 00:59

posia han

Messages: 43
Registered: December 2012

Member

Hi Alex,
we found that if we use autrun on cgsl ,and then we use testexec command :testexec -c .xml (change the autconfig parameter to autid),and it works. Maybe i think that there is no problem with the xml file, but the time between start the AUT and run the testsuit is a little short? We need to run the test suit remotely, could you give us some suggestions?

Report message to a moderator

Re: testexec from Windows connect to linux AUT failed at the end [message #1003871 is a reply to message #1003778]

Tue, 22 January 2013 07:05

Alexandra Schladebeck

Messages: 1613
Registered: July 2009

Senior Member

Ah, thanks for the extra information. Timing is indeed an issue here - there is more information on this bug entry. Basically, the synchronization between starting the Agent, the AUT via autrun and the test is something that, depending on your system and the size of your AUT, may have to be done with a couple of little scripts at the moment.

Hope that helps!

Alex

Report message to a moderator

Previous Topic:	Getting error while using environment variables
Next Topic:	AUT Agent on AIX ,couldn't start AUT with Excutable File name such as .sh file

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Fri Apr 19 06:04:51 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter