Eclipse Community Forums: Jubula » RCP AUT

Help

Home

Home » Archived » Jubula » RCP AUT - Unable to Map Objects

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

RCP AUT - Unable to Map Objects [message #1741263]

Wed, 24 August 2016 09:14

aki khan

Messages: 1
Registered: August 2016

Junior Member

Hi Guys,

Hoping you can help.

I cannot map the objects of the AUT.

The application is RCP, stole this format from a previous user.

description:

* started aut-agent (as administrator)
* started jubula
* opened test with use cases
* connect to aut-agent
-> status line notes: Connected to AUT Agent localhost:60000
* start aut -> running aut opens correctly and shown in Running AUTs window
-> no logs so far
* start object mapping mode
-> Unassigned component names window opens,
but after some seconds in console the message appears:
OK: Connection to AUT could not be established.
-> green highlithing was not seen in aut
-> mapping with key was not successful

----------------------------

messages in client.log:
----------------------------
2016-08-24 10:43:36.902 [Worker-4] ERROR o.e.j.c.c.c.AUTConnection - Connection to AUT could not be established.
2016-08-24 10:44:00.076 [Worker-7] ERROR o.e.j.c.c.c.AUTConnection - Connection to AUT could not be established.
2016-08-24 10:57:17.434 [Worker-9] ERROR o.e.j.c.c.c.AUTConnection - Connection to AUT could not be established.
2016-08-24 11:06:00.613 [Worker-12] ERROR o.e.j.c.c.c.AUTConnection - Connection to AUT could not be established.
2016-08-24 11:06:09.264 [main] ERROR o.e.j.c.ui.utils.ErrorHandlingUtil - An error has occurred.
org.eclipse.jubula.tools.internal.exception.JBException: No AUT is running.
at org.eclipse.jubula.client.ui.rcp.handlers.StopObjectMappingModeHandler.execute(StopObjectMappingModeHandler.java:35) [org.eclipse.jubula.client.ui.rcp_4.0.0.201607281404.jar:na]
at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:295) [org.eclipse.ui.workbench_3.107.1.v20160120-2131.jar:na]
at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90) [org.eclipse.ui.workbench_3.107.1.v20160120-2131.jar:na]
at sun.reflect.GeneratedMethodAccessor451.invoke(Unknown Source) ~[na:na]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_66]
at java.lang.reflect.Method.invoke(Method.java:497) ~[na:1.8.0_66]
at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56) [org.eclipse.e4.core.di_1.5.0.v20150421-2214.jar:na]
at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:252) [org.eclipse.e4.core.di_1.5.0.v20150421-2214.jar:na]
at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:234) [org.eclipse.e4.core.di_1.5.0.v20150421-2214.jar:na]
at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132) [org.eclipse.e4.core.contexts_1.4.0.v20150828-0818.jar:na]
at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:152) [org.eclipse.e4.core.commands_0.11.0.v20150422-0725.jar:na]
at org.eclipse.core.commands.Command.executeWithChecks(Command.java:493) [org.eclipse.core.commands_3.7.0.v20150422-0725.jar:na]
at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:486) [org.eclipse.core.commands_3.7.0.v20150422-0725.jar:na]
at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210) [org.eclipse.e4.core.commands_0.11.0.v20150422-0725.jar:na]
at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:799) [org.eclipse.e4.ui.workbench.renderers.swt_0.13.0.v20150901-1347.jar:na]
at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.handleWidgetSelection(HandledContributionItem.java:675) [org.eclipse.e4.ui.workbench.renderers.swt_0.13.0.v20150901-1347.jar:na]
at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.access$7(HandledContributionItem.java:659) [org.eclipse.e4.ui.workbench.renderers.swt_0.13.0.v20150901-1347.jar:na]
at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem$4.handleEvent(HandledContributionItem.java:592) [org.eclipse.e4.ui.workbench.renderers.swt_0.13.0.v20150901-1347.jar:na]
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) [org.eclipse.swt.win32.win32.x86_64_3.104.2.v20160212-1350.jar:na]
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4362) [org.eclipse.swt.win32.win32.x86_64_3.104.2.v20160212-1350.jar:na]
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1113) [org.eclipse.swt.win32.win32.x86_64_3.104.2.v20160212-1350.jar:na]
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4180) [org.eclipse.swt.win32.win32.x86_64_3.104.2.v20160212-1350.jar:na]
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3769) [org.eclipse.swt.win32.win32.x86_64_3.104.2.v20160212-1350.jar:na]
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127) [org.eclipse.e4.ui.workbench.swt_0.13.0.v20150504-0621.jar:na]
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) [org.eclipse.core.databinding.observable_1.5.0.v20150422-0725.jar:na]
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018) [org.eclipse.e4.ui.workbench.swt_0.13.0.v20150504-0621.jar:na]
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156) [org.eclipse.e4.ui.workbench_1.3.1.v20160203-0951.jar:na]
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:694) [org.eclipse.ui.workbench_3.107.1.v20160120-2131.jar:na]
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) [org.eclipse.core.databinding.observable_1.5.0.v20150422-0725.jar:na]
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:606) [org.eclipse.ui.workbench_3.107.1.v20160120-2131.jar:na]
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) [org.eclipse.ui.workbench_3.107.1.v20160120-2131.jar:na]
at org.eclipse.jubula.app.Launcher.start(Launcher.java:217) [org.eclipse.jubula.app_4.0.0.201607281404/:na]
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) [org.eclipse.equinox.app_1.3.300.v20150423-1356.jar:na]
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) [org.eclipse.osgi_3.10.102.v20160118-1700.jar:na]
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) [org.eclipse.osgi_3.10.102.v20160118-1700.jar:na]
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380) [org.eclipse.osgi_3.10.102.v20160118-1700.jar:na]
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235) [org.eclipse.osgi_3.10.102.v20160118-1700.jar:na]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_66]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_66]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_66]
at java.lang.reflect.Method.invoke(Method.java:497) ~[na:1.8.0_66]
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669) [org.eclipse.equinox.launcher_1.3.100.v20150511-1540.jar:na]
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608) [org.eclipse.equinox.launcher_1.3.100.v20150511-1540.jar:na]
at org.eclipse.equinox.launcher.Main.run(Main.java:1515) [org.eclipse.equinox.launcher_1.3.100.v20150511-1540.jar:na]
at org.eclipse.equinox.launcher.Main.main(Main.java:1488) [org.eclipse.equinox.launcher_1.3.100.v20150511-1540.jar:na]
----------------------------

* try to stop object mapping mode -> Error window
-------------------------
An error occurred.
Reason: 3004:Unexpected error occurred.
Details: No AUT is running.
-------------------------

-> aut is running ok
-> status line still shows: Connected to AUT Agent localhost:60000.
-> aut is still shown in Running AUTs window

Thanks guys

Report message to a moderator

Re: RCP AUT - Unable to Map Objects [message #1741379 is a reply to message #1741263]

Wed, 24 August 2016 14:48

Alexandra Schladebeck

Messages: 1613
Registered: July 2009

Senior Member

Hi there,

it could be the case that the version of the RCP accessor you are using is not compatible with the version of the AUT Agent you are using. The migration instructions (Including for an an RCP accessor) are here:
http://testing.bredex.de/migration-information.html

Otherwise, can you provide the following info:
- what version of Eclipse does your application use (and with, or without the compatibility layer)
- what version of Jubula are you using (and standalone or Eclipse for Testers)
- do you have any custom extensions installed for your application?

Thanks,
Alex

Report message to a moderator

Previous Topic:	Jubula 8.3 Standalone
Next Topic:	maximize screen of the AUT

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Wed Sep 18 23:36:16 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter