Eclipse Community Forums: Test and Performance Tools Platform (TPTP) » No info on java.util.* package objects in memory profiler

Home » Archived » Test and Performance Tools Platform (TPTP) » No info on java.util.* package objects in memory profiler

No info on java.util.* package objects in memory profiler [message #45170]

Thu, 08 December 2005 09:54

Eclipse User

Originally posted by: dbranley.dharbor.com

Yesterday I upgraded to Eclipse 3.1.1 and installed the latest release of
TPTP. Install and initial experience went very smoothly. The tutorials
were very helpful. I'm profiling a Java application that I am "attaching"
to. This happens to be a WebLogic domain. Everything seems to be working
fine and when I review the results of the Basic Memory Analysis I can see
all of my packages listed along with packages from weblogic, cots, and
java's default package (primitives) and a few classes in java.lang.*. But
what is missing is all other java packages. Most notably missing is stats
for java.lang.String and everything from java.lang.util.*. I'm trying to
profile Strings and HashMaps, so not having stats for this is a problem.
I don't have any filters on the data, so I know that is not the problem.

Any idea what I might be doing wrong? Is this a known bug or WAD?

thanks,
Dan

Re: No info on java.util.* package objects in memory profiler [message #45201 is a reply to message #45170]

Thu, 08 December 2005 10:26

Eclipse User

Originally posted by: Navid_Mehregani_nmehrega.ca.ibm.com

This is a multipart message in MIME format.
--=_alternative 0054D456852570D1_=
Content-Type: text/plain; charset="US-ASCII"

I just profiled a small class by including the java* packages and it seems
to be working.

Are you absolutely sure you're not using any filters? By default, the
profiling sets use a default filter set that excludes the java* packages,
but some of the java.lang* classes still show up even though this filter
set is used. Please double check this by selecting your launch
configuration -> select the 'Profiling' tab -> Select your profiling set
-> Edit -> Next -> Next -> Make sure the filter set you're using doesn't
exclude the java* packages.

Also, can you please give us more information:

- Which JDK version are you using? (Make sure you try it with JDK 1.4)
- Are you profiling with IAC or RAC? (If you're profiling with IAC, try
using the RAC)
- You also mentioned you're attaching to your profiling agent. Are you
running your application under enabled or controlled mode? 'HashMap'
won't show up if you're running under enabled mode. Try running your
application under controlled mode.

Navid Mehregani
--=_alternative 0054D456852570D1_=
Content-Type: text/html; charset="US-ASCII"

 I just profiled a small class by including
the java* packages and it seems to be working.
 
 Are you absolutely sure you're not using
any filters?  By default, the profiling sets use a default filter
set that excludes the java* packages, but some of the java.lang* classes
still show up even though this filter set is used.  Please double
check this by selecting your launch configuration -> select the 'Profiling'
tab -> Select your profiling set -> Edit -> Next -> Next ->
Make sure the filter set you're using doesn't exclude the java* packages.
 
 Also, can you please give us more information:
 
 - Which JDK version are you using?  (Make
sure you try it with JDK 1.4)
 - Are you profiling with IAC or RAC?
  (If you're profiling with IAC, try using the RAC)
 - You also mentioned you're attaching
to your profiling agent.  Are you running your application under enabled
or controlled mode?  'HashMap' won't show up if you're running under
enabled mode.  Try running your application under controlled mode.
 
 Navid Mehregani
--=_alternative 0054D456852570D1_=--

Re: No info on java.util.* package objects in memory profiler [message #45229 is a reply to message #45201]

Thu, 08 December 2005 10:39

Eclipse User

Originally posted by: dbranley.dharbor.com

That was it, I didn't have the filtering configured correctly. I think
what confused me was that I was confusing the Filtering of the Memory
Statistics after the data is collected with the Filtering of what to
collect. Both of these concepts are called "Filtering".

Thanks for the help. Now I see all my String objects :)

-Dan

Re: No info on java.util.* package objects in memory profiler [message #45414 is a reply to message #45229]

Thu, 08 December 2005 15:29

Eclipse User

Originally posted by: Navid_Mehregani_nmehrega.ca.ibm.com

This is a multipart message in MIME format.
--=_alternative 007087D2852570D1_=
Content-Type: text/plain; charset="US-ASCII"

I'm glad that solved your problem.

Yes, both of those concepts are referred to as filtering. One is
filtering on the agent *before* data has been collected and the other is
filtering on the views *after* data has been collected.

Navid Mehregani
--=_alternative 007087D2852570D1_=
Content-Type: text/html; charset="US-ASCII"

 I'm glad that solved your problem.
 
 Yes, both of those concepts are referred
to as filtering.  One is filtering on the agent *before* data has
been collected and the other is filtering on the views *after* data has
been collected.
 
 Navid Mehregani
--=_alternative 007087D2852570D1_=--

Previous Topic:	AGR on Eclipse 3.0.x?
Next Topic:	Jboss 4.0.4 and TPTP 4.1

Goto Forum:

-=] Back to Top [=-

Current Time: Mon Sep 01 02:41:29 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter