Home » Archived » Test and Performance Tools Platform (TPTP) » Agent Controller Confusion
| Agent Controller Confusion [message #78317] |
Fri, 21 July 2006 19:17  |
Eclipse User |
|
|
|
Originally posted by: eric.kolotyluk.creo.com
When I tried to profile my application I get
Security Message
Connection failed on host localhost.
Reason:
IWAT0284E The agent controller is not available on host local host.
Make sure that:
* the agent controller is installed.
* the agent controller is configured to communicate with your machine.
* you have the correct host name and port number for the agent controller.
I've been reading through the on-line help for Agent Controller.
Was it deliberately made confusing for a reason? There's a lot of
information on what do do, but little information or examples on how to do
it.
Was it too difficult to just make this stuff work out of the box?
1) How do I know if agent controller is installed? Where is it supposed to
go? If it's not installed, where do I get it from? Why was in not included
in the basic TFTP install?
2) The configuration instruction are based on the asumption that you know
the answers to (1), but the documentation does not address (1).
3) Same as (2).
Is there a tutorial somewhere with examples?
Cheers, Eric
|
|
|
| Re: Agent Controller Confusion [message #78331 is a reply to message #78317] |
Fri, 21 July 2006 20:25  |
| Eclipse User |
|
|
|
Originally posted by: eric.kolotyluk.creo.com
OK, so I found some documentation on the Integrated Agent Controller, yet
there is noting in the user interface to select it, or to tell you if it's
enabled or available. When I follow the on-line instructions for launching
a Java Application it always errors out complaining about the Agent
Controller.
Does anyone have any suggestions on what to try next?
It would be nice if TFTP were as easy to use as the NetBeans profiler.
Then it would also be nice if the NetBeans profiler worked all the time.
Cheers, Eric
Integrated Agent Controller
In the past, TPTP workbench users would need the services of the
standalone Agent Controller before they could use the function in the
Profiling and Logging perspective and in the Test perspective. Even when
the user tried to profile a Java application locally or to run TPTP Tests
locally, the Agent Controller would have to be installed on the local
machine.
The Integrated Agent Controller is a new feature in TPTP workbench which
allows users to profile a Java application locally and to run a TPTP Test
locally without needing the standalone Agent Controller on the local
machine. Profiling on a remote machine or running a TPTP test on a remote
machine would still need the Agent Controller on that remote machine. The
biggest benefit of having Integrated Agent Controller is to simplify the
usage of TPTP functionalities in the local scenario by removing the
dependencies on the local Agent Controller. There is no need to install
and configure the local Agent Controller when using the Profiling and
Logging perspective and Test perspective locally.
The Integrated Agent Controller provides the entry-level functionalities
of the standalone Agent Controller. To get the full functionalities, the
standalone Agent Controller is still the way to go.
This feature is packaged in the TPTP Platform Runtime install image and
therefore no separate install step is required. The Integrated Agent
Controller does not require any configuration at all. Unlike the Agent
Controller, which requires the user to enter information such as the path
for the Java executable, the Integrated Agent Controller will determine
the required information from Eclipse workbench during startup.
|
|
|
| Re: Agent Controller Confusion [message #78346 is a reply to message #78317] |
Fri, 21 July 2006 21:33 |
| Eclipse User |
|
|
|
Eric Kolotyluk wrote:
> When I tried to profile my application I get
How did you try to profile it? Profile... => Java Application?
> Security Message
> Connection failed on host localhost.
Was there somewhere you had a choice and you chose the "localhost:10002"
option? Because that requires a (separate) agent controller, and you're
not running that. You'd want the "Local Direct Connection" option, if
given a choice. But those options are normally not seen through this
route... for "Statistical monitoring" (e.g., PerfmonAgent execution)
yes, but not for profiling.
> Reason:
> IWAT0284E The agent controller is not available on host local host.
> Make sure that:
> * the agent controller is installed.
> * the agent controller is configured to communicate with your machine.
> * you have the correct host name and port number for the agent controller.
>
> I've been reading through the on-line help for Agent Controller.
>
> Was it deliberately made confusing for a reason? There's a lot of
> information on what do do, but little information or examples on how to
> do it.
Sure, it was our whole goal in life to make your life miserable! :-)
I'm not sure why things are the way they are... there are efforts to
make them better. Some say the whole IAC (integrated agent controller)
was such an effort; IM(not-so)HO it's been more of a hindrance than a help!
Also in my experience, the "examples on how to do" things are found in
the EclipseCon (and other) conference tutorials and the like under
tutorials on the Documents page.
> Was it too difficult to just make this stuff work out of the box?
Given all the TPTP is trying to do, it is tough. *If* it were just a
profiler, that would be one thing. We could do that solely, cleanly,
etc. ... but that wasn't the first and foremost goal. Adding the IAC so
as to MAKE that task (and a few others) simple for people like you that
don't need/want an (non-Integrated)AC just didn't work the way we hoped
(again, my opinion).
> 1) How do I know if agent controller is installed? Where is it supposed
> to go? If it's not installed, where do I get it from? Why was in not
> included in the basic TFTP install?
The way to know if it is running is to look at the running processes for
a process called RAServer[.exe] (for Linx and <4.2 for Windows) or
ACServer[.exe] for 4.2 Windows. How to know if it is installed? If it's
your box, you'd probably know if you installed it.
Where do you get it from? If you go to TPTP's home page (<
http://www.eclipse.org/tptp >) and go to the Downloads link, you'll get
our download pages. By default, I think 4.2.0 should be visible. If you
get a page with a selection of downloads, pick stable/development as you
prefer, but get to a specific download page. Such a page will have a
table of TPTP downloads at the top (Runtime and SDKs) ... this is what
you get/got from Callisto via the Callisto Discovery site. It has the
Eclipse workbench components for TPTP and, with the introduction of the
IAC in 4.1.0, abilities to run some agents without an AC.
Prior to that time, and anytime things "go wrong" for IAC use (which is
way too often), you'll get suggestions to "use the RAC" or "download an
agent controller". ... Scrolling down the download page you'll find a
bunch of "tech preview" stuff way down that is fun to peruse and
contemplate using, but between that "experimental" stuff and the "main
event" at the top are a set of links to "native logging" and "agent
controllers".
Here's the rub. A bunch of that stuff is "native code" ... specific to a
platform (hardware architecture and most likely OS as well). It's not
"write once run everywhere" Java code... it's often written in C/C++
(some even in assembler, believe it or not). That requires
system-specific downloads.
Down at the bottom of that download page are links to things like the
"Installation Guide for 4.2.0" ... read it! It might help a lot.
So, you see... it couldn't be in a "run everywhere" download as was the
TPTP Runtime. (The Eclipse Platform itself is the same way... some parts
are system dependent!)
> 2) The configuration instruction are based on the asumption that you
> know the answers to (1), but the documentation does not address (1).
I think much of the installation expectations preceded the use of the
Update Manager (UM), or at least did not assume the universal use of the
UM for Callisto. Before Callisto, people got TPTP by coming through our
download page, reading the download instructions, and piecing together
what they needed. Then, the problem was getting them to handle the
pre-requisites (EMF&XSD primarily). UM does that for you.
But now we have people "dropping in" on TPTP without the proper pointers!
> 3) Same as (2).
>
> Is there a tutorial somewhere with examples?
>
> Cheers, Eric
On that Download page (or perhaps inside the Installation Guide if not
there) are links to the "Getting Started with the Agent Controller".
That, too, will be helpful. And/or see the Help => Help Contents =>
"Working with the agent controller" I think it is.
*If* all you ever want to do is profile Java code on your own system,
the hope and expectation was that you'd just use the IAC and never even
have to worry about the AC. The AC was left for "the big guys" that
wanted to do *remote* monitoring/profiling/tracing/logging/etc. Guys
that wanted to do just the local stuff didn't need a "heavyweight" AC
dragging them down; they should be able to do it "in process". Now we
have the in process solution, but at the least trouble we have to tell
people to go use the (remote) agent controller instead.
--
RDS
Randy D. Smith randy (dot) d (dot) smith (at) intel (dot) com
Eclipse TPTP Committer, Platform Proj (data collection/agent controller)
|
|
|
| Re: Agent Controller Confusion [message #78362 is a reply to message #78331] |
Fri, 21 July 2006 21:41 |
| Eclipse User |
|
|
|
Eric Kolotyluk wrote:
> OK, so I found some documentation on the Integrated Agent Controller,
> yet there is noting in the user interface to select it, or to tell you
> if it's enabled or available. When I follow the on-line instructions for
> launching a Java Application it always errors out complaining about the
> Agent Controller.
To select it: The idea was that it would be selected by default, or
"turn itself off" if it "saw" that a remote agent controller was already
there (it could tell either due to port 10002 already being taken, or if
certain named pipes were already claimed).
What you're looking for is in Window => Preferences... =>
AgentController => Integrated Agent Controller.
> Does anyone have any suggestions on what to try next?
A couple of options... start back with "what you did" and let us help
you get it working with the IAC; or, install the AC and let us try to
help you get it working that way.
> It would be nice if TFTP were as easy to use as the NetBeans profiler.
> Then it would also be nice if the NetBeans profiler worked all the time.
How is its system monitoring? (PerfmonAgent, LinuxAgent, monitoring of
various web/app servers etc.) And its ability to let you
peruse/filter/sort log files and the like? And the ability to
monitor/profile/log remotely on a variety of systems? Netbeans profiler
is like a one-blade knife, while TPTP is like a Swiss Army Knife.
Personally, I'd like us to turn TPTP into something like my
Leatherman... best of both worlds! If you agree, start filing those
bugzillas and push hard on the "usability argument". Consider continuing
that plea in eclipse.foundation where some of us are arguing that "ease
of use" is *the* big issue for now. ... or that it's not, and it's the
extendability you get that makes for great *products built on top of
Eclipse&etc.* That debate is on-going.
> Cheers, Eric
>
> Integrated Agent Controller
> In the past, TPTP workbench users would need the services of the
> standalone Agent Controller before they could use the function in the
> Profiling and Logging perspective and in the Test perspective. Even when
> the user tried to profile a Java application locally or to run TPTP
> Tests locally, the Agent Controller would have to be installed on the
> local machine.
> The Integrated Agent Controller is a new feature in TPTP workbench which
> allows users to profile a Java application locally and to run a TPTP
> Test locally without needing the standalone Agent Controller on the
> local machine. Profiling on a remote machine or running a TPTP test on a
> remote machine would still need the Agent Controller on that remote
> machine. The biggest benefit of having Integrated Agent Controller is to
> simplify the usage of TPTP functionalities in the local scenario by
> removing the dependencies on the local Agent Controller. There is no
> need to install and configure the local Agent Controller when using the
> Profiling and Logging perspective and Test perspective locally.
> The Integrated Agent Controller provides the entry-level functionalities
> of the standalone Agent Controller. To get the full functionalities,
> the standalone Agent Controller is still the way to go.
>
>
> This feature is packaged in the TPTP Platform Runtime install image and
> therefore no separate install step is required. The Integrated Agent
> Controller does not require any configuration at all. Unlike the Agent
> Controller, which requires the user to enter information such as the
> path for the Java executable, the Integrated Agent Controller will
> determine the required information from Eclipse workbench during startup.
>
>
Yeah, I find a LOT of our documentation makes a lot of sense once you
understand the stuff it's talking about! :-) :-(
--
RDS
Randy D. Smith randy (dot) d (dot) smith (at) intel (dot) com
Eclipse TPTP Committer, Platform Proj (data collection/agent controller)
|
|
|
| Re: Agent Controller Confusion [message #78405 is a reply to message #78362] |
Fri, 21 July 2006 23:32 |
| Eclipse User |
|
|
|
Originally posted by: eric.kolotyluk.creo.com
Randy D. Smith wrote:
> Eric Kolotyluk wrote:
>> OK, so I found some documentation on the Integrated Agent Controller,
>> yet there is noting in the user interface to select it, or to tell you
>> if it's enabled or available. When I follow the on-line instructions for
>> launching a Java Application it always errors out complaining about the
>> Agent Controller.
> To select it: The idea was that it would be selected by default, or
> "turn itself off" if it "saw" that a remote agent controller was already
> there (it could tell either due to port 10002 already being taken, or if
> certain named pipes were already claimed).
> What you're looking for is in Window => Preferences... =>
> AgentController => Integrated Agent Controller.
OK, that helps. When I went to the preferences all the UI controls were
disabled, and integrated agent was not selected. I clicked the "restore
defaults" button and integrated agent was selected and all the controls
were enabled.
I tried running my application but got
Could not resolve to JVMPI interface
FATAL ERROR: JVMPI, an experimental interface, is no longer supported.
Please use the supported interface: the JVM Tool Interface (JVM TI).
For information on temporary workarounds contact: jvmpi_eol@sun.com
Error occurred during initialization of VM
-Xrun library failed to init: piAgent
I noticed in the preferences setting the following
Java executable (JAVA_PATH):
C:\Program Files\Java\jre1.6.0\bin\java.exe
Is that what it should be, or should it be configured for jre1.5?
>> Does anyone have any suggestions on what to try next?
> A couple of options... start back with "what you did" and let us help
> you get it working with the IAC; or, install the AC and let us try to
> help you get it working that way.
I can't remember exactly what I did, but I'm pretty sure I selected the
class in my application with main, and then selected "profile" from the
"run" menu, then clicked the "profile" button.
I can't remember if I did anything to explicity turn off IAC; noting
obvious comes to mind.
I'll see if I can install Eclipse 3.2 and TFTP fresh (maybe under Vista)
and see if I can reproduce the problem.
>> It would be nice if TFTP were as easy to use as the NetBeans profiler.
>> Then it would also be nice if the NetBeans profiler worked all the time.
> How is its system monitoring? (PerfmonAgent, LinuxAgent, monitoring of
> various web/app servers etc.) And its ability to let you
> peruse/filter/sort log files and the like? And the ability to
> monitor/profile/log remotely on a variety of systems? Netbeans profiler
> is like a one-blade knife, while TPTP is like a Swiss Army Knife.
> Personally, I'd like us to turn TPTP into something like my
> Leatherman... best of both worlds! If you agree, start filing those
> bugzillas and push hard on the "usability argument". Consider continuing
> that plea in eclipse.foundation where some of us are arguing that "ease
> of use" is *the* big issue for now. ... or that it's not, and it's the
> extendability you get that makes for great *products built on top of
> Eclipse&etc.* That debate is on-going.
Since I haven't really used TFTP yet I can't really compare the feature to
NetBeans yet. Before NetBeans I used OptimizeIt. Netbeans was way more
easy to configure and start than OptimizeIt, and I found it gave me
important information more clearly sooner.
Unfortunately with NetBeans one day it just stopped working with my
application. I asked for help from the NetBeans newsgroup, someone asked
me a few questions, I replied and heard nothing further from them.
I appreciate the goal to create a swiss army knife, but I've found that
when developing software it's best to start simple first, and add features
later (on top of a solid foundation). Given usability vs features, I'll
always go with usability because what good are features if it's too
difficult to even get the product working. I'll look in to giving feedback
in the appropriate forums as you suggest. I really do want to make Eclipse
my one-stop-shopping IDE.
>> Cheers, Eric
>>
>> Integrated Agent Controller
>> In the past, TPTP workbench users would need the services of the
>> standalone Agent Controller before they could use the function in the
>> Profiling and Logging perspective and in the Test perspective. Even when
>> the user tried to profile a Java application locally or to run TPTP
>> Tests locally, the Agent Controller would have to be installed on the
>> local machine.
>> The Integrated Agent Controller is a new feature in TPTP workbench which
>> allows users to profile a Java application locally and to run a TPTP
>> Test locally without needing the standalone Agent Controller on the
>> local machine. Profiling on a remote machine or running a TPTP test on a
>> remote machine would still need the Agent Controller on that remote
>> machine. The biggest benefit of having Integrated Agent Controller is to
>> simplify the usage of TPTP functionalities in the local scenario by
>> removing the dependencies on the local Agent Controller. There is no
>> need to install and configure the local Agent Controller when using the
>> Profiling and Logging perspective and Test perspective locally.
>> The Integrated Agent Controller provides the entry-level functionalities
>> of the standalone Agent Controller. To get the full functionalities,
>> the standalone Agent Controller is still the way to go.
>>
>>
>> This feature is packaged in the TPTP Platform Runtime install image and
>> therefore no separate install step is required. The Integrated Agent
>> Controller does not require any configuration at all. Unlike the Agent
>> Controller, which requires the user to enter information such as the
>> path for the Java executable, the Integrated Agent Controller will
>> determine the required information from Eclipse workbench during startup.
>>
>>
> Yeah, I find a LOT of our documentation makes a lot of sense once you
> understand the stuff it's talking about! :-) :-(
That's what I figured as I was reading the documentation. It's always a
good idea to get a herd of idiots using your stuff to keep you honest ;-)
Fortunately I'm in idiot mode right now.
Cheers, Eric
|
|
|
| Re: Agent Controller Confusion [message #78420 is a reply to message #78405] |
Sat, 22 July 2006 01:10 |
| Eclipse User |
|
|
|
Eric Kolotyluk wrote:
> Randy D. Smith wrote:
>
>> Eric Kolotyluk wrote:
>
>> What you're looking for is in Window => Preferences... =>
>> AgentController => Integrated Agent Controller.
>
>
> OK, that helps. When I went to the preferences all the UI controls were
> disabled, and integrated agent was not selected. I clicked the "restore
> defaults" button and integrated agent was selected and all the controls
> were enabled.
>
> I tried running my application but got
>
> Could not resolve to JVMPI interface
> FATAL ERROR: JVMPI, an experimental interface, is no longer supported.
> Please use the supported interface: the JVM Tool Interface (JVM TI).
> For information on temporary workarounds contact: jvmpi_eol@sun.com
> Error occurred during initialization of VM
> -Xrun library failed to init: piAgent
>
> I noticed in the preferences setting the following
>
> Java executable (JAVA_PATH):
> C:\Program Files\Java\jre1.6.0\bin\java.exe
>
> Is that what it should be, or should it be configured for jre1.5?
1.5... Sun deprecated JVMPI ... if you go and look at that TPTP download
page, you'll find a JVMTI (note the P=>T) Tech Preview profiler download
that supports Sun's next profiling interface. 1.5 is supposed to support
both, but 1.6 and beyond will only support JVMTI.
But don't take the JVMTI Tech Preview as it doesn't work with 1.6 (yet),
just 1.5.
> I appreciate the goal to create a swiss army knife, but I've found that
> when developing software it's best to start simple first, and add
> features later (on top of a solid foundation). Given usability vs
> features, I'll always go with usability because what good are features
> if it's too difficult to even get the product working. I'll look in to
> giving feedback in the appropriate forums as you suggest. I really do
> want to make Eclipse my one-stop-shopping IDE.
Agreed.
Move the setting back to a 1.5 jre and try profiling again.
--
RDS
Randy D. Smith randy (dot) d (dot) smith (at) intel (dot) com
Eclipse TPTP Committer, Platform Proj (data collection/agent controller)
|
|
|
| Re: Agent Controller Confusion [message #78447 is a reply to message #78420] |
Sat, 22 July 2006 17:03 |
| Eclipse User |
|
|
|
Originally posted by: eric.kolotyluk.creo.com
Randy D. Smith wrote:
> Eric Kolotyluk wrote:
>> Randy D. Smith wrote:
>>
>>> Eric Kolotyluk wrote:
>>
>>> What you're looking for is in Window => Preferences... =>
>>> AgentController => Integrated Agent Controller.
>>
>>
>> OK, that helps. When I went to the preferences all the UI controls were
>> disabled, and integrated agent was not selected. I clicked the "restore
>> defaults" button and integrated agent was selected and all the controls
>> were enabled.
>>
>> I tried running my application but got
>>
>> Could not resolve to JVMPI interface
>> FATAL ERROR: JVMPI, an experimental interface, is no longer supported.
>> Please use the supported interface: the JVM Tool Interface (JVM TI).
>> For information on temporary workarounds contact: jvmpi_eol@sun.com
>> Error occurred during initialization of VM
>> -Xrun library failed to init: piAgent
>>
>> I noticed in the preferences setting the following
>>
>> Java executable (JAVA_PATH):
>> C:Program FilesJavajre1.6.0binjava.exe
>>
>> Is that what it should be, or should it be configured for jre1.5?
> 1.5... Sun deprecated JVMPI ... if you go and look at that TPTP download
> page, you'll find a JVMTI (note the P=>T) Tech Preview profiler download
> that supports Sun's next profiling interface. 1.5 is supposed to support
> both, but 1.6 and beyond will only support JVMTI.
> But don't take the JVMTI Tech Preview as it doesn't work with 1.6 (yet),
> just 1.5.
I set the IAC preferences to Java 1.5 but I still get the same JVMPI
error. I tried quiting Eclipse and restarting (on a hunch) but that didn't
help.
One thing I did notice is that whenever I restart Eclipse, IAC is
disabled. I'm pretty sure at this point Eclipse 3.2 does not think IAC
should be enabled by default, nor can it remember that it has been
enabled. Another problem is that whenever you click the "restore defaults"
button, it always sets the JVM back to 1.6. I hate to be the bearer of bad
news, but I don't think TPTP is ready for prime time yet.
So where do I go from here?
Cheers, Eric
>> I appreciate the goal to create a swiss army knife, but I've found that
>> when developing software it's best to start simple first, and add
>> features later (on top of a solid foundation). Given usability vs
>> features, I'll always go with usability because what good are features
>> if it's too difficult to even get the product working. I'll look in to
>> giving feedback in the appropriate forums as you suggest. I really do
>> want to make Eclipse my one-stop-shopping IDE.
> Agreed.
> Move the setting back to a 1.5 jre and try profiling again.
|
|
|
| Re: Agent Controller Confusion [message #78462 is a reply to message #78447] |
Sat, 22 July 2006 17:56 |
| Eclipse User |
|
|
|
Eric Kolotyluk wrote:
> I set the IAC preferences to Java 1.5 but I still get the same JVMPI
> error. I tried quiting Eclipse and restarting (on a hunch) but that
> didn't help.
>
> One thing I did notice is that whenever I restart Eclipse, IAC is
> disabled. I'm pretty sure at this point Eclipse 3.2 does not think IAC
> should be enabled by default, nor can it remember that it has been
> enabled. Another problem is that whenever you click the "restore
> defaults" button, it always sets the JVM back to 1.6. I hate to be the
> bearer of bad news, but I don't think TPTP is ready for prime time yet.
> So where do I go from here?
>
> Cheers, Eric
It's not just the "compatibility setting" that needs to say Java 1.5;
you actually have to be running under a 1.5 JRE. You can start eclipse
with "-vm <path to 1.5 JRE>" or change the JRE that it actually uses in
the prefs... let's see... under Window => Preferences... Java =>
Compiler you'll see the "compliance level", but it's the Java =>
Installed JREs that actually show the JRE used. So there or -vm on
command line, but you'll need a 1.5 JRE. 1.6 ones will enforce the
JVMPI=>JVMTI transition.
See what happens with the IAC enablement and the default restoration
when actually run under Java 1.5, okay?
--
RDS
Randy D. Smith randy (dot) d (dot) smith (at) intel (dot) com
Eclipse TPTP Committer, Platform Proj (data collection/agent controller)
|
|
|
| Re: Agent Controller Confusion [message #78477 is a reply to message #78462] |
Sat, 22 July 2006 18:36 |
| Eclipse User |
|
|
|
Randy D. Smith wrote:
> Eric Kolotyluk wrote:
>
>> I set the IAC preferences to Java 1.5 but I still get the same JVMPI
>> error. I tried quiting Eclipse and restarting (on a hunch) but that
>> didn't help.
>>
>> One thing I did notice is that whenever I restart Eclipse, IAC is
>> disabled. I'm pretty sure at this point Eclipse 3.2 does not think IAC
>> should be enabled by default, nor can it remember that it has been
>> enabled. Another problem is that whenever you click the "restore
>> defaults" button, it always sets the JVM back to 1.6. I hate to be the
>> bearer of bad news, but I don't think TPTP is ready for prime time yet.
>
>
>> So where do I go from here?
>>
>> Cheers, Eric
>
>
> It's not just the "compatibility setting" that needs to say Java 1.5;
> you actually have to be running under a 1.5 JRE. You can start eclipse
> with "-vm <path to 1.5 JRE>" or change the JRE that it actually uses in
> the prefs... let's see... under Window => Preferences... Java =>
> Compiler you'll see the "compliance level", but it's the Java =>
> Installed JREs that actually show the JRE used. So there or -vm on
> command line, but you'll need a 1.5 JRE. 1.6 ones will enforce the
> JVMPI=>JVMTI transition.
>
> See what happens with the IAC enablement and the default restoration
> when actually run under Java 1.5, okay?
>
I'm sorry ... I was thinking the "compatibility setting" as in the
Window => Preferences... => Java => Compiler one... you're saying you
set the Windows => Preferences... => Agent Controller => Integrated
Agent Controller => Java executable (JAVA_PATH) to point to a Java 1.5?
If so, and you still get a warning about JVMPI not being supported, I
really need to file a bugzilla on this, and you'll need to go to using a
separate AC!
--
RDS
Randy D. Smith randy (dot) d (dot) smith (at) intel (dot) com
Eclipse TPTP Committer, Platform Proj (data collection/agent controller)
|
|
|
| Re: Agent Controller Confusion [message #78577 is a reply to message #78477] |
Mon, 24 July 2006 11:27 |
| Eclipse User |
|
|
|
Originally posted by: eric.kolotyluk.creo.com
Randy D. Smith wrote:
> Randy D. Smith wrote:
>> Eric Kolotyluk wrote:
>>
>>> I set the IAC preferences to Java 1.5 but I still get the same JVMPI
>>> error. I tried quiting Eclipse and restarting (on a hunch) but that
>>> didn't help.
>>>
>>> One thing I did notice is that whenever I restart Eclipse, IAC is
>>> disabled. I'm pretty sure at this point Eclipse 3.2 does not think IAC
>>> should be enabled by default, nor can it remember that it has been
>>> enabled. Another problem is that whenever you click the "restore
>>> defaults" button, it always sets the JVM back to 1.6. I hate to be the
>>> bearer of bad news, but I don't think TPTP is ready for prime time yet.
>>
>>
>>> So where do I go from here?
>>>
>>> Cheers, Eric
>>
>>
>> It's not just the "compatibility setting" that needs to say Java 1.5;
>> you actually have to be running under a 1.5 JRE. You can start eclipse
>> with "-vm <path to 1.5 JRE>" or change the JRE that it actually uses in
>> the prefs... let's see... under Window => Preferences... Java =>
>> Compiler you'll see the "compliance level", but it's the Java =>
>> Installed JREs that actually show the JRE used. So there or -vm on
>> command line, but you'll need a 1.5 JRE. 1.6 ones will enforce the
>> JVMPI=>JVMTI transition.
>>
>> See what happens with the IAC enablement and the default restoration
>> when actually run under Java 1.5, okay?
>>
> I'm sorry ... I was thinking the "compatibility setting" as in the
> Window => Preferences... => Java => Compiler one... you're saying you
> set the Windows => Preferences... => Agent Controller => Integrated
> Agent Controller => Java executable (JAVA_PATH) to point to a Java 1.5?
Yes, that's right, that's where I set the runntime to 1.5.
> If so, and you still get a warning about JVMPI not being supported, I
> really need to file a bugzilla on this, and you'll need to go to using a
> separate AC!
Acting on you previous post I started Eclipse with -vm "C:\Program
Files\Java\jre1.5.0_06\bin\java" and this time it worked. Also, when
Eclipse started, IAC was enabled. I think before it was detecting that it
was running under JRE 1.6 and automatically disabled IAC. However, there
are still several problems:
1) I think it should have been sufficient to set the JRE in Windows =>
Preferences => Agent Conroller => Integrated Agent Controller => Java
executable (as you said). Also, if this is set to a compatible runtime,
then IAC should not be disabled when Eclipse starts.
2) When I start Eclipse with -vm it opens a Windows command window -
what's up with that?
3) When my application is running, I cannot monitor the Execution
Statistics or Memory Statistics tabs because every time a line is sent to
the console, the console tab becomes active (hiding the other tabs).
4) When the window for my appliation appears, I cannot control it. Every
time I click on it I get a "beep" and nothing happens.
Cheers, Eric
|
|
|
| Re: Agent Controller Confusion [message #78660 is a reply to message #78577] |
Mon, 24 July 2006 14:26 |
| Eclipse User |
|
|
|
Eric Kolotyluk wrote:
> Randy D. Smith wrote:
>
>> Randy D. Smith wrote:
>>
>>> Eric Kolotyluk wrote:
>>>
>>>> I set the IAC preferences to Java 1.5 but I still get the same JVMPI
>>>> error. I tried quiting Eclipse and restarting (on a hunch) but that
>>>> didn't help.
>>>>
>>>> One thing I did notice is that whenever I restart Eclipse, IAC is
>>>> disabled. I'm pretty sure at this point Eclipse 3.2 does not think
>>>> IAC should be enabled by default, nor can it remember that it has
>>>> been enabled. Another problem is that whenever you click the
>>>> "restore defaults" button, it always sets the JVM back to 1.6. I
>>>> hate to be the bearer of bad news, but I don't think TPTP is ready
>>>> for prime time yet.
>>>
>>>
>>>
>>>> So where do I go from here?
>>>>
>>>> Cheers, Eric
>>>
>>>
>>>
>>> It's not just the "compatibility setting" that needs to say Java 1.5;
>>> you actually have to be running under a 1.5 JRE. You can start
>>> eclipse with "-vm <path to 1.5 JRE>" or change the JRE that it
>>> actually uses in the prefs... let's see... under Window =>
>>> Preferences... Java => Compiler you'll see the "compliance level",
>>> but it's the Java => Installed JREs that actually show the JRE used.
>>> So there or -vm on command line, but you'll need a 1.5 JRE. 1.6 ones
>>> will enforce the JVMPI=>JVMTI transition.
>>>
>>> See what happens with the IAC enablement and the default restoration
>>> when actually run under Java 1.5, okay?
>>>
>
>> I'm sorry ... I was thinking the "compatibility setting" as in the
>> Window => Preferences... => Java => Compiler one... you're saying you
>> set the Windows => Preferences... => Agent Controller => Integrated
>> Agent Controller => Java executable (JAVA_PATH) to point to a Java 1.5?
>
>
> Yes, that's right, that's where I set the runntime to 1.5.
>
>> If so, and you still get a warning about JVMPI not being supported, I
>> really need to file a bugzilla on this, and you'll need to go to using
>> a separate AC!
>
>
> Acting on you previous post I started Eclipse with -vm "C:\Program
> Files\Java\jre1.5.0_06\bin\java" and this time it worked. Also, when
> Eclipse started, IAC was enabled. I think before it was detecting that
> it was running under JRE 1.6 and automatically disabled IAC. However,
> there are still several problems:
>
> 1) I think it should have been sufficient to set the JRE in Windows =>
> Preferences => Agent Conroller => Integrated Agent Controller => Java
> executable (as you said). Also, if this is set to a compatible runtime,
> then IAC should not be disabled when Eclipse starts.
I'm not sure I agree... that preference is "the Java the IAC will use to
spawn off JVM invocations" vs. what the -vm argument changes, "the Java
used to run the Eclipse workbench (and therefore the IAC itself, it
being a plugin to that workbench)".
> 2) When I start Eclipse with -vm it opens a Windows command window -
> what's up with that?
I'm not sure... I presume it's a "Windows thing" ... taking a wild stab
in the dark I wonder if the reference to "C:\...\java" has to be given
to a CMD interpreter for indirect forking whereas if you explicitly said
"C:\...\java.exe" it wouldn't need that interpreter but instead would be
forked off directly?
> 3) When my application is running, I cannot monitor the Execution
> Statistics or Memory Statistics tabs because every time a line is sent
> to the console, the console tab becomes active (hiding the other tabs).
I presume this is a matter of personal preference... you can go back and
see the stats, right? I think many would WANT to have the behavior
you're seeing.
> 4) When the window for my appliation appears, I cannot control it. Every
> time I click on it I get a "beep" and nothing happens.
What's the nature of the app and what do you mean by "control it"? The
(minor/brief) times I've dabbled in profiling I've been dealing with
console apps ... Perhaps one of the "real profiling gurus" can step in
and help with this, as this is the only one of the four that would
presumably need a bugzilla (imho).
> Cheers, Eric
--
RDS
Randy D. Smith randy (dot) d (dot) smith (at) intel (dot) com
Eclipse TPTP Committer, Platform Proj (data collection/agent controller)
|
|
| |
| Re: Agent Controller Confusion [message #78777 is a reply to message #78660] |
Tue, 25 July 2006 11:53 |
| Eclipse User |
|
|
|
Originally posted by: eric.kolotyluk.creo.com
Randy D. Smith wrote:
> Eric Kolotyluk wrote:
>> Randy D. Smith wrote:
>>
>>> Randy D. Smith wrote:
>>>
>>>> Eric Kolotyluk wrote:
>>>>
>>>>> I set the IAC preferences to Java 1.5 but I still get the same JVMPI
>>>>> error. I tried quiting Eclipse and restarting (on a hunch) but that
>>>>> didn't help.
>>>>>
>>>>> One thing I did notice is that whenever I restart Eclipse, IAC is
>>>>> disabled. I'm pretty sure at this point Eclipse 3.2 does not think
>>>>> IAC should be enabled by default, nor can it remember that it has
>>>>> been enabled. Another problem is that whenever you click the
>>>>> "restore defaults" button, it always sets the JVM back to 1.6. I
>>>>> hate to be the bearer of bad news, but I don't think TPTP is ready
>>>>> for prime time yet.
>>>>
>>>>
>>>>
>>>>> So where do I go from here?
>>>>>
>>>>> Cheers, Eric
>>>>
>>>>
>>>>
>>>> It's not just the "compatibility setting" that needs to say Java 1.5;
>>>> you actually have to be running under a 1.5 JRE. You can start
>>>> eclipse with "-vm <path to 1.5 JRE>" or change the JRE that it
>>>> actually uses in the prefs... let's see... under Window =>
>>>> Preferences... Java => Compiler you'll see the "compliance level",
>>>> but it's the Java => Installed JREs that actually show the JRE used.
>>>> So there or -vm on command line, but you'll need a 1.5 JRE. 1.6 ones
>>>> will enforce the JVMPI=>JVMTI transition.
>>>>
>>>> See what happens with the IAC enablement and the default restoration
>>>> when actually run under Java 1.5, okay?
>>>>
>>
>>> I'm sorry ... I was thinking the "compatibility setting" as in the
>>> Window => Preferences... => Java => Compiler one... you're saying you
>>> set the Windows => Preferences... => Agent Controller => Integrated
>>> Agent Controller => Java executable (JAVA_PATH) to point to a Java 1.5?
>>
>>
>> Yes, that's right, that's where I set the runntime to 1.5.
>>
>>> If so, and you still get a warning about JVMPI not being supported, I
>>> really need to file a bugzilla on this, and you'll need to go to using
>>> a separate AC!
>>
>>
>> Acting on you previous post I started Eclipse with -vm "C:Program
>> FilesJavajre1.5.0_06binjava" and this time it worked. Also, when
>> Eclipse started, IAC was enabled. I think before it was detecting that
>> it was running under JRE 1.6 and automatically disabled IAC. However,
>> there are still several problems:
>>
>> 1) I think it should have been sufficient to set the JRE in Windows =>
>> Preferences => Agent Conroller => Integrated Agent Controller => Java
>> executable (as you said). Also, if this is set to a compatible runtime,
>> then IAC should not be disabled when Eclipse starts.
> I'm not sure I agree... that preference is "the Java the IAC will use to
> spawn off JVM invocations" vs. what the -vm argument changes, "the Java
> used to run the Eclipse workbench (and therefore the IAC itself, it
> being a plugin to that workbench)".
OK, I can go along with that. It would help if there were better
diagnostics that could guide the user to resolving the problem correctly.
>> 2) When I start Eclipse with -vm it opens a Windows command window -
>> what's up with that?
> I'm not sure... I presume it's a "Windows thing" ... taking a wild stab
> in the dark I wonder if the reference to "C:...java" has to be given
> to a CMD interpreter for indirect forking whereas if you explicitly said
> "C:...java.exe" it wouldn't need that interpreter but instead would be
> forked off directly?
I forgot to use javaw instead of java (which opens a console window). I
think frustration leads to dumbness :-)
>> 3) When my application is running, I cannot monitor the Execution
>> Statistics or Memory Statistics tabs because every time a line is sent
>> to the console, the console tab becomes active (hiding the other tabs).
> I presume this is a matter of personal preference... you can go back and
> see the stats, right? I think many would WANT to have the behavior
> you're seeing.
OK, this was more of a problem with the default Profiling and Logging
perspective. I moved the Console tab to the bottom tile of my perspective
so I could view the other tabs. This should be the default layout for this
perspective (like it is for the Java perspective).
>> 4) When the window for my appliation appears, I cannot control it. Every
>> time I click on it I get a "beep" and nothing happens.
> What's the nature of the app and what do you mean by "control it"? The
> (minor/brief) times I've dabbled in profiling I've been dealing with
> console apps ... Perhaps one of the "real profiling gurus" can step in
> and help with this, as this is the only one of the four that would
> presumably need a bugzilla (imho).
OK, after the problem happening a few more times it went away for no
apparent reason. The app is a GUI with a main window. The first few times
the window would appear. I could grab the title bar of the window and move
it around, but none of the controls in the window would function, and ever
time I clicked in the window (even to move it) I would get a system beep.
I am not able to reproduce this problem any more.
I've been following the Tutorial: Analyzing profiling data, and for some
reason I cannot get Execution Flow view and table to appear. When I
right-click in the Profiling Monitor view and select => open with, there
is no Execution Flow item in the menu. Am I missing some configuration or
preference setting somewhere to get this to appear.
The other thing I find disconcerting is that when the application is
running, the other profiling views are all static, the data does not
change over time. In NetBeans, similar views had dynamic data that was
changing as the application ran. Is this normal for TPTP? The problem is
that TPTP is giving me no feedback that it is actually monitoring anything
which makes it appear broken.
Am I the only person that is having this much trouble with TPTP? When I
tried the profiler in NetBeans I figured it all out in about 10 minutes
without any help from anyone else. In about 20 minutes I was getting
useful results I could use to help understand my application. After
starting with TPTP, 3 days later, and with much (appreciated) assistance I
have yet to get anything useful out of it. Where's the best place to lobby
for usability being the top priority? I would strongly encouage the TPTP
leadership to checkout NetBeans for usability ideas.
Cheers, Eric
|
|
| |
| Re: Agent Controller Confusion [message #79870 is a reply to message #78777] |
Thu, 03 August 2006 16:36 |
| Eclipse User |
|
|
|
Eric Kolotyluk wrote:
> Randy D. Smith wrote:
>
>> Eric Kolotyluk wrote:
>>
>>> Randy D. Smith wrote:
>>>
>>>> Randy D. Smith wrote:
>>>>
>>>>> Eric Kolotyluk wrote:
>>>>> . . .
>
> Am I the only person that is having this much trouble with TPTP? When I
> tried the profiler in NetBeans I figured it all out in about 10 minutes
> without any help from anyone else. In about 20 minutes I was getting
> useful results I could use to help understand my application. After
> starting with TPTP, 3 days later, and with much (appreciated) assistance
> I have yet to get anything useful out of it. Where's the best place to
> lobby for usability being the top priority? I would strongly encouage
> the TPTP leadership to checkout NetBeans for usability ideas.
>
> Cheers, Eric
Just in case anyone follows this thread here, I'm noting that Eric has
"escalated" the discussion over to eclipse.foundation. Presumably you
might want to join the thread over there.
--
RDS
Randy D. Smith randy (dot) d (dot) smith (at) intel (dot) com
Eclipse TPTP Committer, Platform Proj (data collection/agent controller)
|
|
|
Goto Forum:
Current Time: Wed Jun 18 19:14:54 EDT 2025
Powered by FUDForum. Page generated in 0.11170 seconds |
Home