Hi LeO, Regarding your first question, the answer is Yes - you can create a batch file and set the aforementioned variables. Another option is to make sure that none of these variables are globally defined. They are not required when launching the Agent Controller, but if they exist and point to invalid location, it can cause problems.
I also recommend trying to launch the JVMTI Profiler from a command prompt, not from the Eclipse workbench, in order to find out whether your problem is really with the Agent Controller. Some clarifications: a) TPTP_AC_HOME should point to the installation directory of the Agent Controller (the directory that includes the 'bin' directory), not to the directory containing RAServer.exe b) JAVA_PROFILER_HOME should point to the directory where the JVMTI Profiler runtime files are located (JPIBootLoader.dll, JPI.dll and their friends). The path suggested by Guru is correct. The 'plugins' directory you see is the one located in the Agent Controller installation directory (TPTP_AC_HOME from the previous item), not the Eclipse 'plugins' directory. c+d) Make perfect sense to me. Make sure that the RASERVER_HOME variable is *not* defined anywhere. It is used by an old AC version and may cause problems. If you have it globally defined, remove it. Now for your biggest questions :) : What we ask you to do here is to launch the JVMTI Profiler *outside* the Eclipse workbench, so we can understand whether the problem is with the *profiler* or with the *Agent Controller*. To do that, you don't have to build a JAR, just know the following information about your applications: 1) The output directory in which the compiled .class files are stored. If you use source folders, this directory is probably <project root>\bin. If not, then this directory is simply <project root>. 2) Any external JAR files you use with your Java application. These are listed in the "Java Build Path" > "Libraries" page of your Eclipse project (right click the project name and select "Properties"...). Armed with this information, please try the following: a) Open command prompt and make sure that the Java VM is in your path (type java -version and check whether you get an error or a printout of the Java version). b) CD to the Eclipse project output directory (described in step 1 above). c) Type "java <app name>" where <app name> is the fully qualified name of the Java class implementing the 'main' function of your application. For example, if this class name is mypackage.MyApp then type: java mypackage.MyApp Check whether your Java application executes successfully. If not, do not proceed to the next step. Go back and try to understand why it fails. Most likely the current directory is wrong or some additional JARs (mentioned in step 2 above) are missing and you should add them with the -cp option of the 'java' executable. d) Set the environment variables as described in Guru's message (JAVA_PROFILER_HOME, PATH) and modify the command typed in step c) above to be the following: java -agentlib:JPIBootLoader=JPIAgent:server=standalone;CGProf <app name> This will launch <app name> with the Call Graph JVMTI profiler. When execution completes, a file named trace.trcxml will be generated in the current directory. e) Go to the Eclipse workbench, select "File | Import" from the menu, select the "Profiling and Logging" > "Profiling file" option and follow the instructions to import the trace.trcxml mentioned in the previous step. Then switch to the Profiling and Logging perspective and view the profiling results. Finally, if you get in trouble launching your application from command line, repeat the above steps with a simpler Java application (a one class app such as HelloWorld will do). Please let us know whether you succeeded. Thanks, Asaf -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of LeO Welsch Sent: Thursday, January 25, 2007 10:24 AM To: tptp-tracing-profiling-tools-dev@eclipse.org Subject: RE: [tptp-tracing-profiling-tools-dev] Profiling with Mustang Guru, I am little bit confused about the parameter-settings: Currently I am launching the AC-Server via Explorer. What you suggest would mean that either I set the Environment-variables gloablly or within a Batch-File, valid only for the AC-Server. But is it sufficient to set it only for the AC-Server? >a) Set TPTP_AC_HOME=<<Agent Controller Home>> Means, where the AC-Server is located? The directory from which I start the AC-Server? So, anywhere on my Disk? >b) Set >JAVA_PROFILER_HOME=%TPTP_AC_HOME%\plugins\org.eclipse.tptp.javaprofiler Reading this, then the TPTP_AC_HOME must be the Eclipse-Home-Directory. Right? Sorry, I am confused, cause a+b does not meat ;) the current configuration. >c) Set PATH=%JAVA_PROFILER_HOME%;%PATH%;%TPTP_AC_HOME%\bin >d) Set PATH=%PATH%;%JAVA_HOME%\bin c+d makes sense??? What about the mentioned RASERVER_HOME? This is currently set to the dir, which has 'tptpAgentCtlr.exe' in it. Is this correct? >e) Execute the following command: > java -agentlib:JPIBootLoader=JPIAgent:server=standalone;CGProf <<Your > Application to profile>> Hm' and NOW the BIGGEST question of all: How to specify the 'application to profile', if it is in the Project within Eclipse? Does it mean I have to build a JAR, to collect the data? Does it mean, I am unable to collect data within Eclipse? If not, how and where do I have to specify these parameters in the Profiling-option? ???? LeO >From: "Nagarajan, Guru" <[EMAIL PROTECTED]> >Reply-To: TPTP Tracing and Profiling Tools Project developer >discussions<tptp-tracing-profiling-tools-dev@eclipse.org> >To: "TPTP Tracing and Profiling Tools Project developer >discussions"<tptp-tracing-profiling-tools-dev@eclipse.org> >Subject: RE: [tptp-tracing-profiling-tools-dev] Profiling with Mustang >Date: Wed, 24 Jan 2007 13:28:13 -0800 > >Leo, > I mentioned to you in my last posting that I was able to recreate this >issue. I was able to recreate this issue on a machine that had >Environment variables that are consumed by the Profiler. The environment >variable I had that was not pointing to my test installation and this >caused the JVMTI agent to be not available. > >Can you look into environment variables on your machine and the PATH >setting. >I would suggest you to verify if the following environment variables are >pointing to the right location >a) RASERVER_HOME >b) TPTP_AC_HOME >c) JAVA_HOME (points to a Java 15) >d) JAVA_PROFILER_HOME > >If the above check on the environmental variable does not work for you >can you try running the profiler from the command line. >a) Set TPTP_AC_HOME=<<Agent Controller Home>> >b) Set >JAVA_PROFILER_HOME=%TPTP_AC_HOME%\plugins\org.eclipse.tptp.javaprofiler >c) Set PATH=%JAVA_PROFILER_HOME%;%PATH%;%TPTP_AC_HOME%\bin >d) Set PATH=%PATH%;%JAVA_HOME%\bin >e) Execute the following command: > java -agentlib:JPIBootLoader=JPIAgent:server=standalone;CGProf <<Your > Application to profile>> > >Let us know if this helps. > >Thanks, >Guru > > >-----Original Message----- >From: [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED] On Behalf >Of Yaffe, Asaf >Sent: Sunday, January 21, 2007 12:15 AM >To: TPTP Tracing and Profiling Tools Project developer discussions >Subject: RE: [tptp-tracing-profiling-tools-dev] Profiling with Mustang > >Hi LeO, > >A) Eclipse stability issues are likely caused by the fact that you are >using development builds and not stable builds. I strongly suggest you >will switch to Eclipse 3.2.1 and TPTP 4.3. As for the error you see in >the log file, I am not sure what these mean. I know there are some >missing message strings in the JVMTI Client code. There is a bug open >for that (https://bugs.eclipse.org/bugs/show_bug.cgi?id=164630). I think >you can safely ignore these errors. > >B) The New Agent Controller must be launched before you try to launch >the profiler. You may experience AC connection problems that are caused >by the weird timeout issues we currently have with the New AC (known >issue). Try to follow these steps (I find it helpful): >1. Start the new AC >2. From Eclipse, go to the Profile Launch Configuration for you >application, switch to the Monitor tab, select the "Java Profiler with >Instrumentation" data collector and click the "Test Availability" >button. You should get the following message: "The connection was >successful!". If not, try again. If this still does not work, check >again (I know this is starting to sound like a broken record, sorry >about that) that the default AC port in the "Profiling and Logging" >preferences page is set to 10006 and try again. If you manage to get the >"success" message, you are good to go. If not... then I guess that you >should consider "downgrading" your Java environment to 5.0 (1.5) and use >the old Java Profiler, which does not require the AC at all (make sure >to shut down AC before doing that). > >Last but not least, it does make more sense to continue this discussion >on the newsgroup. The newsgroup visibility is better and there is a >chance that more people from the community will participate. Please post >any further issues to the eclipse.tptp newsgroup (I am monitoring this >newsgroup on a daily basis). > >Thanks, >Asaf > > >-----Original Message----- >From: [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED] On Behalf >Of LeO Welsch >Sent: Thursday, January 18, 2007 3:52 PM >To: tptp-tracing-profiling-tools-dev@eclipse.org >Subject: RE: [tptp-tracing-profiling-tools-dev] Profiling with Mustang > >Asaf, > >Most of the things mentioned here I begin to understand. > >I would be very happy, if after each restart Eclipse would be THAT >stable to >all the time the same Error. I think it's a moving target, nevertheless >let's try to hit it anyhow. > >Only about 1) of your response the JVMTI client: > >I reviewed the installation and the package is already unpacked and >installed there. > >A) When I launch Eclipse I get: > >!ENTRY org.eclipse.core.resources 2 1 2007-01-18 14:15:39.288 >!MESSAGE Skipping builder 'com.ibm.sse.model.structuredbuilder' for >project >'YLA_Planer'. Either the builder is missing from the install, or it >belongs >to a project nature that is missing or disabled. > >!ENTRY org.eclipse.osgi 2 1 2007-01-18 14:20:29.578 >!MESSAGE NLS unused message: ERROR_TI_MODEL_CREATION in: >org.eclipse.tptp.platform.jvmti.client.internal.messages > >!ENTRY org.eclipse.osgi 2 1 2007-01-18 14:20:29.578 >!MESSAGE NLS unused message: TASK_CONNECTING_TO_AGENT; in: >org.eclipse.tptp.platform.jvmti.client.internal.messages > >!ENTRY org.eclipse.osgi 2 1 2007-01-18 14:20:29.588 >!MESSAGE NLS missing message: TASK_CONNECTING_TO_AGENT in: >org.eclipse.tptp.platform.jvmti.client.internal.messages > >(Note: I try to profile project 'YLA_Profile' and not 'YLA_Planer'!!!) > > >===> means what??? I should start the AgentController first, before >launching Eclipse or not? I am thinking about this due to the messages. > >B) When I try to launch my application, I get: 'The JVMTI agent >org.eclipse.tptp.jvmti is not available. Make sure that the agent's >libraries are available and that it is configured properly.'? (With a >blank >Textarea in it.) > >What does this mean? > >C) Reviewing the installed Plugins I find the following entry: > >'TPTP JVMTI Profiler Client Version: 4.2.0.v200611150100' > >does this fit with the 4.4? And please note: I have downloaded the >complete >package on Mon. 15! > >LeO > >P.S.: Does it make sense to discuss this isse further on the Newsgroup >or >via PM? > > > >From: "Yaffe, Asaf" <[EMAIL PROTECTED]> > >Reply-To: TPTP Tracing and Profiling Tools Project developer > >discussions<tptp-tracing-profiling-tools-dev@eclipse.org> > >To: "TPTP Tracing and Profiling Tools Project developer > >discussions"<tptp-tracing-profiling-tools-dev@eclipse.org> > >Subject: RE: [tptp-tracing-profiling-tools-dev] Profiling with Mustang > >Date: Thu, 18 Jan 2007 14:46:57 +0200 > > > >LeO, > > > >1) JPIBootLoader.dll is part of the JVMTI Profiler runtime component > >(Agent Controller extension). On the TPTP 4.4 download page, it is > >located under "Technology Previews > The New Java Profiler > JVMTI >Agent > >Controller Extension". Use the drop-down list to pick the appropriate > >platform (Windows IA-32 in your case?). When download completes, unzip > >the archive to the New Technology Agent Controller installation > >directory. Make sure to use a "real" unzip utility (e.g. WinZip) and > >turn-on the "Use Folder Names" option so that the files will be > >extracted to their correct location (assuming the New Tech AC is > >installed on c:\ntac, the files should be extracted to > >c:\ntac\plugins\org.eclipse.tptp.javaprofiler). > > > >_________________________________________________________________ >Laugh, share and connect with Windows Live Messenger >http://clk.atdmt.com/MSN/go/msnnkwme0020000001msn/direct/01/?href=http: / >/imagine-msn.com/messenger/launch80/default.aspx?locale=en-us&source=hm t >agline > >_______________________________________________ >tptp-tracing-profiling-tools-dev mailing list >tptp-tracing-profiling-tools-dev@eclipse.org >https://dev.eclipse.org/mailman/listinfo/tptp-tracing-profiling-tools-d e >v >_______________________________________________ >tptp-tracing-profiling-tools-dev mailing list >tptp-tracing-profiling-tools-dev@eclipse.org >https://dev.eclipse.org/mailman/listinfo/tptp-tracing-profiling-tools-d e >v >_______________________________________________ >tptp-tracing-profiling-tools-dev mailing list >tptp-tracing-profiling-tools-dev@eclipse.org >https://dev.eclipse.org/mailman/listinfo/tptp-tracing-profiling-tools-d ev _________________________________________________________________ Express yourself instantly with MSN Messenger! Download today it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/ _______________________________________________ tptp-tracing-profiling-tools-dev mailing list tptp-tracing-profiling-tools-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/tptp-tracing-profiling-tools-de v _______________________________________________ tptp-tracing-profiling-tools-dev mailing list tptp-tracing-profiling-tools-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/tptp-tracing-profiling-tools-dev
