Hi,
>I've seen a few threads regarding the OutOfMemory problems. Has it
been
>decided that reloading webapps is one of the causes of this?
No, and such a decision could never be made.
>And, if
>so, would an undeploy and a new deploy fix that issue?
No.
Yoav
This e-mail, including any atta
program as to whether you reach out of
memory with reloading but I am no expert in this area by any means.
Allistair.
> -Original Message-
> From: Shapira, Yoav [mailto:[EMAIL PROTECTED]
> Sent: 23 November 2004 14:05
> To: Tomcat Users List
> Subject: RE: OutOfMemory exception
On Tue, 2004-11-23 at 09:05, Shapira, Yoav wrote:
> No, and such a decision could never be made.
OK. So, reloading webapps should clean up items in memory consumed by
that particular webapp, then?
Do you know of a good memory profiler that can be run while webapps are
up and return to me what ea
November 2004 14:12
> To: Tomcat Users List
> Subject: RE: OutOfMemory exceptions
>
>
> On Tue, 2004-11-23 at 09:05, Shapira, Yoav wrote:
> > No, and such a decision could never be made.
>
> OK. So, reloading webapps should clean up items in memory consumed by
> th
Hi,
>OK. So, reloading webapps should clean up items in memory consumed by
>that particular webapp, then?
Yes and no. You are vastly oversimplifying the real world here. It's
extremely difficult to come up with a webapp that can truly be reloaded
without a memory loss.
>Do you know of a good
On Tue, 2004-11-23 at 09:17, Shapira, Yoav wrote:
> Yes and no. You are vastly oversimplifying the real world here. It's
> extremely difficult to come up with a webapp that can truly be reloaded
> without a memory loss.
Would undeploying the webapp follow the same route (meaning some memory
loss
Hi,
>Would undeploying the webapp follow the same route (meaning some memory
>loss)?
Undeploying without redeploying should always reduce memory usage. But
it won't take away all the memory used by the app most likely.
>What profilers do you use?
I like OptimizeIt. JProbe is good too, as are
On Tuesday 23 November 2004 16:03, Ryan Daly wrote:
> All:
Hi,
> I've seen a few threads regarding the OutOfMemory problems. Has it been
> decided that reloading webapps is one of the causes of this? And, if
> so, would an undeploy and a new deploy fix that issue?
Check the memory usage of you
I read in another thread about setting up one Tomcat instance per host.
Is that something you'd recommend doing? At least then a redeploy
wouldn't affect other webapps running on that same host...
Maybe this should be another thread if it gets much attention.
--
This sounds like your sessions arent getting invalidated. If you look at the tomcat
manager app it will tell you how many there are and you are likely to see this number
increasing. The reason that it starts bloated is because when you shutdown the
sessions get serialised and then reloaded once
Conference Call Services, LLC
-Original Message-
From: Dale, Matt [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 17, 2004 2:07 PM
To: Tomcat Users List
Subject: RE: OutOfMemory Exceptions AGAIN
This sounds like your sessions arent getting invalidated. If you look at the
tomcat manager app
On Tue, Aug 17, 2004 at 02:13:40PM -0400, Nandish Rudra wrote:
: Thanks for the reply. When I get an http request I do not attach any session
: information or create and cookies/httpsessions and not using tomcat
: clustering, would the sessions still be serialized.
You may not explicitly put anyth
t 2004 19:14
To: 'Tomcat Users List'
Subject: RE: OutOfMemory Exceptions AGAIN
Hello Matt,
Thanks for the reply. When I get an http request I do not attach any session
information or create and cookies/httpsessions and not using tomcat
clustering, would the sessions still be serialized. Is
PROTECTED]
Sent: Tuesday, August 17, 2004 4:25 PM
To: Tomcat Users List
Subject: Re: OutOfMemory Exceptions AGAIN
On Tue, Aug 17, 2004 at 02:13:40PM -0400, Nandish Rudra wrote:
: Thanks for the reply. When I get an http request I do not attach any
session
: information or create and cookies
14 matches
Mail list logo
