| Is memory profile supported by new java profiler? [message #90297] |
Thu, 14 December 2006 09:16  |
Eclipse User |
|
|
|
Originally posted by: sanlyfang.gmail.com
I have installed new agent controller as windows service and try to
memory-profile my application which deployed under weblogic 9.2.
I have changed JAVA_PROFILER settings in weblogic env script as follows:
JAVA_PROFILER=-agentlib:JPIBootLoader=JPIAgent:server=standa lone;CGProf
By default, the profile result is generated in the current directory,
which could be imported into eclipse workbench for further investigation.
But it seems only method execution statistics are available, nothing
displayed when I open memory view, I tried to change startup settings from:
=-agentlib:JPIBootLoader=JPIAgent:server=standalone;CGProf
to
=-agentlib:JPIBootLoader=JPIAgent:server=standalone;MemProf
but without success, I am wondering whether memory profile is supported by
new java profiler/new agent controller and if it is true, what's wrong
with my settings?
Thanks!
|
|
|
| Re: Is memory profile supported by new java profiler? [message #90343 is a reply to message #90297] |
Thu, 14 December 2006 10:15  |
| Eclipse User |
|
|
|
Sanly Fang wrote:
> I have installed new agent controller as windows service and try to
> memory-profile my application which deployed under weblogic 9.2.
>
> I have changed JAVA_PROFILER settings in weblogic env script as follows:
> JAVA_PROFILER=-agentlib:JPIBootLoader=JPIAgent:server=standa lone;CGProf
>
> By default, the profile result is generated in the current directory,
> which could be imported into eclipse workbench for further
> investigation. But it seems only method execution statistics are
> available, nothing displayed when I open memory view, I tried to change
> startup settings from:
> =-agentlib:JPIBootLoader=JPIAgent:server=standalone;CGProf
>
> to
> =-agentlib:JPIBootLoader=JPIAgent:server=standalone;MemProf
>
> but without success, I am wondering whether memory profile is supported
> by new java profiler/new agent controller and if it is true, what's
> wrong with my settings?
>
> Thanks!
>
>
The Memory profiler can be launched with the following command line:
-agentlib:JPIBootLoader=JPIAgent:server=standalone;HeapProf
Make sure you use version 4.3. Earlier versions support only CPU Profiling.
The readme file and online docs are outdated. We expect to post updated
versions soon.
HTH,
Asaf
--
Asaf Yaffe
Eclipse TPTP Committer, JVMTI Profiler
|
|
|
Powered by
FUDForum. Page generated in 0.03540 seconds
Home