Home » Eclipse Projects » RCP Testing Tool » RCPTT freezes if program argument -configuration is specified
| RCPTT freezes if program argument -configuration is specified [message #1863353] |
Mon, 29 January 2024 10:25  |
 Matej Kristan
Messages: 3
Registered: January 2024 |
Junior Member |
|
|
As AUT I would like to use eclipse based IDE which is installed in write only folder. This IDE comes with some pre-installed feature which I updated (through p2) before running AUT. Because it is in write only folder feature update goes into configuration location which is specified in eclipse/configuration/config.ini osgi.configuration.area = <location>.
When I started AUT I noticed that pre-installed plugin is not updated, because AUT did not have specified configuration location. I specified configuration location in AUTs configurations with program argument -configuration <location> and that is when my problem arose.
Running AUT with -configuration argument starts IDE with updated plugin, but RCPTT shows 'Progress Information' (Image below) which times out after few minutes and reports that AUT is no responding although AUT is fully responsive.
In RCPTTs workspace/.metadata/.plugins/org.eclipse.pde.core/<AUTs name>/console.log is empty file.
In RCPTTs workspace/.metadata/.log is this
!ENTRY org.eclipse.rcptt.launching.ext 1 0 2024-01-29 10:52:42.823
!MESSAGE RCPTT: Launching AUT: <AUTs name>: AUT command line arguments is set to: [-launcher, C:\eclipse-rcptt\rcptt.ide-2.5.5-nightly-win32.win32.x86_64\rcptt\eclipse.exe, -name, Eclipse, -showsplash, 600, -product, org.eclipse.platform.ide, -data, C:\eclipse-rcptt\rcptt.ide-2.5.5-nightly-win32.win32.x86_64\ws/../aut-<AUTs name>, -configuration, file:C:/eclipse-rcptt/rcptt.ide-2.5.5-nightly-win32.win32.x86_64/ws/.metadata/.plugins/org.eclipse.pde.core/<AUTs name>/, -dev, file:C:/eclipse-rcptt/rcptt.ide-2.5.5-nightly-win32.win32.x86_64/ws/.metadata/.plugins/org.eclipse.pde.core/smartcode/dev.properties, -os, win32, -ws, win32, -arch, x86_64, -consoleLog, -configuration, <LOCALAPPDATA>/eclipse/configuration, -eclipse.keyring, C:\eclipse-rcptt\rcptt.ide-2.5.5-nightly-win32.win32.x86_64\ws\.metadata\.plugins\org.eclipse.pde.core\<AUTs name>/secure_storage, -vm, C:\jdk]
!ENTRY org.eclipse.rcptt.launching.ext 4 0 2024-01-29 11:02:46.963
!MESSAGE RCPTT: Failed to Launch AUT: smartcode cause Timeout error: AUT doesn't respond
!STACK 1
org.eclipse.core.runtime.CoreException: Timeout error: AUT doesn't respond
at org.eclipse.rcptt.internal.launching.ext.Q7ExtLaunchMonitor.doWait(Q7ExtLaunchMonitor.java:167)
at org.eclipse.rcptt.internal.launching.ext.Q7ExtLaunchMonitor.wait(Q7ExtLaunchMonitor.java:93)
at org.eclipse.rcptt.launching.ext.Q7ExternalLaunchDelegate.launch(Q7ExternalLaunchDelegate.java:128)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:806)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:717)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:712)
at org.eclipse.rcptt.internal.launching.ext.ExternalLaunchExecutor.launch(ExternalLaunchExecutor.java:30)
at org.eclipse.rcptt.internal.launching.aut.BaseAut.launch(BaseAut.java:47)
at org.eclipse.rcptt.ui.launching.LaunchUtils$4.run(LaunchUtils.java:383)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122)
!SUBENTRY 1 org.eclipse.rcptt.launching.ext 4 0 2024-01-29 11:02:46.963
!MESSAGE Timeout error: AUT doesn't respond
!ENTRY org.eclipse.rcptt.launching 1 0 2024-01-29 11:02:46.964
!MESSAGE AUT terminated by RCPTT
!ENTRY org.eclipse.rcptt.launching.ext 4 0 2024-01-29 11:02:46.994
!MESSAGE Timeout error: AUT doesn't respond [Updated on: Tue, 30 January 2024 05:51] Report message to a moderator |
|
| |
| Re: RCPTT freezes if program argument -configuration is specified [message #1863420 is a reply to message #1863378] |
Thu, 01 February 2024 12:39  |
Matej Kristan
Messages: 3
Registered: January 2024 |
Junior Member |
|
|
It does not work for me..
I get following errors in <RCPTT_workspace>/.metadata/.log
!ENTRY org.eclipse.rcptt.launching.ext 1 0 2024-02-01 13:27:49.583
!MESSAGE RCPTT: Launching AUT: smartcode: AUT JVM arguments is set to : [-Dosgi.splashPath=platform:/base/plugins/com.tasking.smartcode, -Xms256m, -Xmx2048m, -Declipse.product=com.tasking.smartcode.ide, -DsvnRepoPath=C:/SVNCheckOut, -Dq7id=21b705e4-e0b3-4256-b501-083e3f1828d9, -Dq7EclPort=4002, -Dosgi.framework.extensions=reference:file:org.eclipse.osgi.compatibility.state_1.2.800.v20221116-1440.jar,reference:file:C:\eclipse-rcptt\rcptt.ide-2.5.5-nightly-win32.win32.x86_64\ws\.metadata\.plugins\org.eclipse.pde.core\.bundle_pool\plugins\org.eclipse.equinox.weaving.hook_1.3.100.v20211021-1418.jar, --add-opens, java.base/java.lang=ALL-UNNAMED, --add-modules=ALL-SYSTEM, -Declipse.vmargs=-Dosgi.splashPath=platform:/base/plugins/com.tasking.smartcode
-Xms256m
-Xmx2048m
-Declipse.product=com.tasking.smartcode.ide
-DsvnRepoPath=C:/SVNCheckOut
-Dq7id=21b705e4-e0b3-4256-b501-083e3f1828d9
-Dq7EclPort=4002
-Dosgi.framework.extensions=reference:file:org.eclipse.osgi.compatibility.state_1.2.800.v20221116-1440.jar,reference:file:C:\eclipse-rcptt\rcptt.ide-2.5.5-nightly-win32.win32.x86_64\ws\.metadata\.plugins\org.eclipse.pde.core\.bundle_pool\plugins\org.eclipse.equinox.weaving.hook_1.3.100.v20211021-1418.jar
--add-opens
java.base/java.lang=ALL-UNNAMED
--add-modules=ALL-SYSTEM
]
!ENTRY org.eclipse.rcptt.launching.ext 1 0 2024-02-01 13:27:49.603
!MESSAGE RCPTT: Launching AUT: smartcode: AUT command line arguments is set to: [-launcher, C:\eclipse-rcptt\rcptt.ide-2.5.5-nightly-win32.win32.x86_64\rcptt\eclipse.exe, -name, Eclipse, -showsplash, 600, -product, org.eclipse.platform.ide, -data, C:\eclipse-rcptt\rcptt.ide-2.5.5-nightly-win32.win32.x86_64\ws/../aut-smartcode, -configuration, file:C:/eclipse-rcptt/rcptt.ide-2.5.5-nightly-win32.win32.x86_64/ws/.metadata/.plugins/org.eclipse.pde.core/smartcode/, -dev, file:C:/eclipse-rcptt/rcptt.ide-2.5.5-nightly-win32.win32.x86_64/ws/.metadata/.plugins/org.eclipse.pde.core/smartcode/dev.properties, -os, win32, -ws, win32, -arch, x86_64, -consoleLog, -eclipse.keyring, C:\eclipse-rcptt\rcptt.ide-2.5.5-nightly-win32.win32.x86_64\ws\.metadata\.plugins\org.eclipse.pde.core\smartcode/secure_storage, -vm, C:\ISYSTEM_APPS\jdk]
!ENTRY org.eclipse.rcptt.launching.ext 4 0 2024-02-01 13:28:37.915
!MESSAGE RCPTT: Failed to Launch AUT: smartcode cause Process was terminated while waiting for AUT startup data
!STACK 1
org.eclipse.core.runtime.CoreException: Process was terminated while waiting for AUT startup data
at org.eclipse.rcptt.internal.launching.ext.Q7ExtLaunchMonitor.doWait(Q7ExtLaunchMonitor.java:138)
at org.eclipse.rcptt.internal.launching.ext.Q7ExtLaunchMonitor.wait(Q7ExtLaunchMonitor.java:93)
at org.eclipse.rcptt.launching.ext.Q7ExternalLaunchDelegate.launch(Q7ExternalLaunchDelegate.java:128)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:806)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:717)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:712)
at org.eclipse.rcptt.internal.launching.ext.ExternalLaunchExecutor.launch(ExternalLaunchExecutor.java:30)
at org.eclipse.rcptt.internal.launching.aut.BaseAut.launch(BaseAut.java:47)
at org.eclipse.rcptt.ui.launching.LaunchUtils$4.run(LaunchUtils.java:383)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122)
!SUBENTRY 1 org.eclipse.rcptt.launching.ext 4 7788 2024-02-01 13:28:37.915
!MESSAGE Process was terminated while waiting for AUT startup data
!ENTRY org.eclipse.rcptt.launching.ext 4 7788 2024-02-01 13:28:37.921
!MESSAGE Process was terminated while waiting for AUT startup data
<RCPTT_workspace>/.metadata/.plugins/org.eclipse.pde.core/smartcode
!ENTRY org.eclipse.osgi 4 0 2024-02-01 13:28:33.348
!MESSAGE Application error
!STACK 1
java.lang.IllegalStateException: Unable to acquire application service. Ensure that the org.eclipse.core.runtime bundle is resolved and started (see config.ini).
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:81)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:402)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:255)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:568)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:659)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:596)
at org.eclipse.equinox.launcher.Main.run(Main.java:1467)
at org.eclipse.equinox.launcher.Main.main(Main.java:1440)
<RCPTT_workspace>/.metadata/.plugins/org.eclipse.pde.core/smartcode/org.eclipse.equinox.simpleconfigurator contains line with core.runtime
org.eclipse.core.runtime,3.26.100.v20221021-0005,plugins/org.eclipse.core.runtime_3.26.100.v20221021-0005.jar,4,true |
|
|
Goto Forum:
Current Time: Fri May 03 20:54:37 GMT 2024
Powered by FUDForum. Page generated in 0.03748 seconds |
] 
Search
Help
Register
Login
Home
