|The process launcher seems to be inactive. Restart the Agent Controller and try [message #134886]
||Mon, 25 August 2008 09:50
| Mahesh Maney
Registered: July 2009
we are facing problems with TPTP Profiler and found a similar FAQ here - |
following the same procedure, we ended up with thr below problem.
We have installed TPTP manually from .zip file. The content was about
293MB. It was downloaded from the TPTP site.
After installing and executing the exclipse.exe file, the help menu shows
the following, here is the Version: Eclipse SDK
Build id: M20080221-1800
We are exploring on the TPTP profiler to integrate it with our eclipse,
built on Europa-3.3
As a first step we have a sample code ( CarModel, downloaded from the same
site ) to profile.
We have changed to the perspective to Profiling and Logging. We get the
Exceution analysis Coverage analysis Memory statistics Object
References and Execution Flow views. Under all the views we get the
No execution statistics is available for display.
Either you have no trace selected in the Profiling Monitor view or the
current selection does not contain execution statistic information.
This view is available only if the trace contains execution statistics. To
collect this type of information, on the Profile tab in the Launch
configuration, choose the Execution Time Analysis option.
We followed the link -
to set up agent controller.
We have downloaded the 14.6MB Agent Controller version 4.2.
And after extracting the files to a folder, we have executed the
RAService.exe and ACServer.exe files. Both of these is listed in
And then on the workspace we right click and select Profile as Java
We get Edit launch configuration properties window -> under Monitor tab,
we choose : Java Profiling JRE 1.5 and Execution Time Analysis under
Even after this, we are unable to profile. Reason being, we get the agent
controller error message always
The process launcher seems to be inactive. Restart the Agent Controller
and try again.
org.eclipse.core.runtime.CoreException: The process launcher seems to be
inactive. Restart the Agent Controller and try again.
at java.lang.Thread.run(Unknown Source)
Have missed anything in the process of enabling profiler?
Can anyone help us with this issue?
do let us know how to proceed further.
|Re: The process launcher seems to be inactive. Restart the Agent Controller and try [message #134927 is a reply to message #134886]
||Mon, 25 August 2008 13:54
| Eugene Chan
Registered: July 2009
In your first use case, did you have a successful launch? and how did you
open the profiling views (execution, memory and coverage views)? You will
need to have an Agent Controller running for your profile to work. I would
suggest you try the following to profile:
1. Shut down Eclipse workbench.
2. Shut down Agent Controller.
3. Make sure there is no ACServer.exe nor dangling java.exe process running
on your system.
4. Start Agent Controller, make sure there is no error starting, you can
check out the servicelog.log file under AgentController/config folder.
5. Start Eclispe workbench.
6. Check agent controller connection via Windows > Preferences > Profiling
and Logging > Hosts > Test Connection button.
7. Profile with launch configuration.
8. Open profiling view by double clicking on the analysis type under a
profiling agent in the Profiling Monitor view, or right click on an agent
and select 'Open With' action.
Hope this helps.
"Mahesh Maney" <firstname.lastname@example.org> wrote in message
> we are facing problems with TPTP Profiler and found a similar FAQ here -
> http://dev.eclipse.org/mhonarc/newsLists/news.eclipse.tptp/m sg06482.html
> following the same procedure, we ended up with thr below problem.
> We have installed TPTP manually from .zip file. The content was about
> 293MB. It was downloaded from the TPTP site.
> After installing and executing the exclipse.exe file, the help menu shows
> the following, here is the Version: Eclipse SDK
> Version: 3.3.2
> Build id: M20080221-1800
> We are exploring on the TPTP profiler to integrate it with our eclipse,
> built on Europa-3.3
> As a first step we have a sample code ( CarModel, downloaded from the same
> site ) to profile.
> We have changed to the perspective to Profiling and Logging. We get the
> Exceution analysis
Powered by FUDForum
. Page generated in 0.02531 seconds