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 by
17% or more in 6 months or less! => http://newsletter.JAMMConsulting.com
> -----Original Message-----
> From: Filip Hanik [mailto:[EMAIL PROTECTED]
> Sent: Monday, December 01, 2003 6:37 PM
> To: Tomcat Users List
> Subject: RE: Tag Handler pool eating up Memory (and
> enablePooling is set to false)
>
>
> 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: 'Tomcat-User'
> Subject: Tag Handler pool eating up Memory (and enablePooling
> is set to
> false)
>
>
> Hello:
>
> We have several tomcat servers running an application. The servers
> slow down after a few hours of uptime.
>
> Looking at the memory usage on the servers, we noticed that
> the servers
> seem to be accumulating memory and finally they slow down when
> the memory utilization becomes high.
>
> We are using the IBM JDK 1.4.1 SR1 with Tomcat 4.1.24 on RedHat 9.
>
> Using the heapdump utility from the IBM JDK, I generated a heap dump
> from one of the servers after it had been up for a while.
>
> >From that output, I see these pieces of infromation:
>
> There were a total of 509,235 objects in memory
> taking up 67,992,688 bytes.
>
> There were 436 instances of org/apache/jasper/runtime/TagHandlerPool.
> Tracing all of the references from these TagHandlerPool object,
> they reference a total of 65,010,600 bytes.
>
> This means that almost 97% of the memory usage of Tomcat is being
> referenced from the TagHandlerPool objects.
>
> I have enablePooling set to false in the Tomcat's web.xml in the conf
> directory.
>
> It seems that the enablePooling setting is not preventing Tomcat from
> pooling the tag handlers and they are referencing a lot of memory.
>
> Does that setting work in Tomcat 4.1.24?
>
> Is there any other reason why Tomcat would behave this way?
>
> Thanks,
> Neil
>
> --
> Neil Aggarwal, JAMM Consulting, (972)612-6056, www.JAMMConsulting.com
> FREE! Valuable info on how your business can reduce operating costs by
> 17% or more in 6 months or less! =>
> http://newsletter.JAMMConsulting.com
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
