|
|
Re: 4.5.1 IAC profiling failure: org.eclipse.tptp.jvmti unavailable: JPIBootLoader [message #136777 is a reply to message #136765] |
Fri, 03 October 2008 16:48 |
Steven Emmerson Messages: 9 Registered: July 2009 |
Junior Member |
|
|
Hi Eugene,
Something very strange has happened. The same Eclipse process that
wouldn't profile at the end-of-work yesterday is profiling today at the
beginning-of-work. I didn't do anything in the interim, so I'm at a loss
to explain this. I do have my Eclipse set-up for automatic download of
updates. I wonder if that's the cause. We also have nightly automatic
updates pushed to our workstations for system software (e.g., libraries,
utilities).
I did execute the script
" plugins/org.eclipse.tptp.platform.ac.linux_em64t_4.4.1.v2008 08290100/agent_controller/bin/SetConfig.sh "
while that Eclipse process was running, but I believe I tried profiling
after that and it still didn't work.
Very odd.
I'll answer your questions for the record (and I have a question).
> How did you start the JUnit test class profile?
I clicked on the profiling icon in the toolbar. TPTP knows that the
application is a JUnit class.
> It sounds like the system variable cannot be located by the IAC, which is
> tested and worked.
> If you manually add the system variable and restart Eclipse, does it work
> for you?
Please forgive my ignorance, but what is the "system variable"?
I forgot to mention in my original post that my Java environment is 64-bit
jdk1.6.0_04.
Regards,
Steve Emmerson
|
|
|
Re: 4.5.1 IAC profiling failure: org.eclipse.tptp.jvmti unavailable: JPIBootLoader [message #136822 is a reply to message #136777] |
Mon, 06 October 2008 14:30 |
Eugene Chan Messages: 287 Registered: July 2009 |
Senior Member |
|
|
Hi Steven,
Could you try the following:
1. shutdown Eclipse workbench.
2. run
plugins/org.eclipse.tptp.platform.ac.linux_em64t_4.4.1.v2008 08290100/agent_controller/bin/SetConfig.sh
to setup Agent Controller
3. run
plugins/org.eclipse.tptp.platform.ac.linux_em64t_4.4.1.v2008 08290100/agent_controller/bin/ACServer
to start an standalone Agent Controller.
4. if step 2 and 3 run without error, restart Eclipse workbench and run your
profile.
The system variable I was referring are those varilables configure in the
Agent Controller config file.
Eugene
"Steven Emmerson" <emmerson@ucar.edu> wrote in message
news:32a9fd6c46608e087932bcc2f7dea4f7$1@www.eclipse.org...
> Hi Eugene,
>
> Something very strange has happened. The same Eclipse process that
> wouldn't profile at the end-of-work yesterday is profiling today at the
> beginning-of-work. I didn't do anything in the interim, so I'm at a loss
> to explain this. I do have my Eclipse set-up for automatic download of
> updates. I wonder if that's the cause. We also have nightly automatic
> updates pushed to our workstations for system software (e.g., libraries,
> utilities).
>
> I did execute the script
> " plugins/org.eclipse.tptp.platform.ac.linux_em64t_4.4.1.v2008 08290100/agent_controller/bin/SetConfig.sh "
> while that Eclipse process was running, but I believe I tried profiling
> after that and it still didn't work.
>
> Very odd.
>
> I'll answer your questions for the record (and I have a question).
>
>> How did you start the JUnit test class profile?
>
> I clicked on the profiling icon in the toolbar. TPTP knows that the
> application is a JUnit class.
>
>> It sounds like the system variable cannot be located by the IAC, which is
>> tested and worked.
>> If you manually add the system variable and restart Eclipse, does it work
>> for you?
>
> Please forgive my ignorance, but what is the "system variable"?
>
> I forgot to mention in my original post that my Java environment is 64-bit
> jdk1.6.0_04.
>
> Regards,
> Steve Emmerson
>
|
|
|
|
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03639 seconds