Chris:
Yeah, it's possible (and probable) that the TagHandlerPool
maintains a
reference back to the ServletContext in which it lives. That
might kew
your results. I'm sure that the TagHandlerPool isn't actually
taking up
that much memory.
This is strange. When I created a heap dump
Neil,
This is strange. When I created a heap dump from my server
just now, it does not have any instances of TagHandlerPool
in the heap dump. That is what I expected before, but I still
had them in my last dump.
That is weird. However, you still have a bunch of tag handler instances,
I see...
are you sure this is a tomcat reference holding on to it?
it could be one of your classes as well, you need to run it through a memory
profile in order to find out
Filip
-Original Message-
From: Neil Aggarwal [mailto:[EMAIL PROTECTED]
Sent: Monday, December 01, 2003 2:53 PM
To:
Neil,
are you sure this is a tomcat reference holding on to it?
it could be one of your classes as well, you need to run it through a memory
profile in order to find out
Yeah, it's possible (and probable) that the TagHandlerPool maintains a
reference back to the ServletContext in which it lives.
Filip:
Thanks for the suggestion.
I have been profiling it and I don't see any references from our
code, but I will keep checking.
Thanks,
Neil
--
Neil Aggarwal, JAMM Consulting, (972)612-6056, www.JAMMConsulting.com
FREE! Valuable info on how your business can reduce operating costs
