The technique is similar in TPTP... start your
application-to-be-profiled with the command line arguments that make it
an agent, that is, using the "-XrunpiAgent" parameter. Then you should
see your application show up under the Agents tab when you go to
Profile... => Attach - Java Process.
The more interesting question (in my mind) is how you would know this...
I guess with the right search parameters, you might get a hit that would
get you the answer... but I'm not sure even the answers we give are
given in a way where you'd know they answer your question!
The best information on the command line approach to creating the
profile agent I've seen is in the Getting Started with the Agent
Controller Guide: Eclipse => TPTP => Downloads => Installation Guide =>
Agent Controller Getting Started Guide => <your platform> under
"Invocation of the Java Profiler from the Command Line". There you will
find more on the options at your disposal.
But I have to agree with you... if you don't know where to look for your
answer, you might have trouble finding it! And if you knew where to
look, why would you be asking? :-) It's the documentation catch-22.
--
RDS
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
Of John Pletka
Sent: Sunday, May 07, 2006 4:26 PM
To: tptp-tracing-profiling-tools-dev@eclipse.org
Subject: [tptp-tracing-profiling-tools-dev] Profiling remote OC4J
j2eeapplication
I'm sure this question has already been answered somewhere, but I
can't find the answer anywhere. I'm trying to profile a J2EE based
application running inside an oc4j container. In the past I've used
the EclipseColorer profiler with good results to do this -- just start
oc4j from the commandline with the extra profiler parameters then
attach to it from eclipse. Unfortunately that profiler does not work
with the latest version of eclipse.
I've gone through the TPTF docs and have not found a way to attach to
a remote application for profiling. Is that even possible?
Is the only way to profile a j2ee application involve building a
JavaApplication Run profile? That has been problematic in the past
(much slower startup, annoying classpath errors like the one below,
etc).
Anyway, I'm looking forward to any help you might have on this. I'm
sure this is a common scenario and I'm just not finding the right
docs.
Thanks in advance,
John
oc4j startup error using Eclipse JavaApplication profile
java.lang.IllegalAccessError: tried to access class
com.sun.enterprise.deployment.OrderedSet from class
com.evermind.server.ejb.deployment.BeanDescriptor
_______________________________________________
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
