Users List
Subject: RE: Tomcat 5.0.28 memory leak
> From: Robert Harper [mailto:[EMAIL PROTECTED]
> Subject: RE: Tomcat 5.0.28 memory leak
>
> I have a similar problem with 1.4.2_07-b05. My app runs with
> very little traffic but as time goes on, the system runs out
> of memory
> From: Robert Harper [mailto:[EMAIL PROTECTED]
> Subject: RE: Tomcat 5.0.28 memory leak
>
> I have a similar problem with 1.4.2_07-b05. My app runs with
> very little traffic but as time goes on, the system runs out
> of memory even though there is plenty of idle time for t
arale, Charles R [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 07, 2006 12:26 PM
To: Tomcat Users List
Subject: RE: Tomcat 5.0.28 memory leak
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]
> Subject: Re: Tomcat 5.0.28 memory leak
>
> I am using jdk1.4.0_04 and tomcat 5.0.
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]
> Subject: Re: Tomcat 5.0.28 memory leak
>
> I am using jdk1.4.0_04 and tomcat 5.0.28.
You really need to get off that level ASAP. Use 1.4.2, which fixes
many, many bugs compared to 1.4.0.
- Chuck
THIS COMMUNICAT
|
| cc:
|
|
[EMAIL PROTECTED] wrote:
Yes I am putting it out in the session but I get the error after the
service has broken and at that point its probably trying to persist data???
and that should be serializable.
My issue is why doesthe service break in the first place?
I am just doing refesh on a page sev
: Tomcat Users List
|
| cc:
|
| Subject: Re:
[EMAIL PROTECTED] wrote:
Why do I have to make my class serializable.It is a simple web application
using the "MemberData" class for storing some data???
Because you are pushing it onto the session.
- Gary
-
To unsubscribe, e-
|
| To: "'Tomcat Users List'"
|
| cc:
sday, March 07, 2006 1:09 PM
To: Tomcat Users List
Subject: Re: Tomcat 5.0.28 memory leak
Yes I tried JProbe and during memory debugging I see char[] size going up.If
I look into bug databases there are various reasons.Some talk to
commons-logging others about session persistance.
I am gettin
The error below is because the class aaa.pm.server.beans.MemberData does not
implement java.io.Serializable.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 07, 2006 1:09 PM
To: Tomcat Users List
Subject: Re: Tomcat 5.0.28 memory leak
Yes I
|
| cc:
|
| Subject:
[EMAIL PROTECTED] wrote:
> Hello All,
>
> I posted this question before.I am using tomcat5.0.28 somehow my
> application blows the service with memory increasing really quicly even
> with one user.
> If I test same on tomcat 4.1.24 it runs fine.
> Any known leaks with this version ???I think tomca
Hello All,
I posted this question before.I am using tomcat5.0.28 somehow my
application blows the service with memory increasing really quicly even
with one user.
If I test same on tomcat 4.1.24 it runs fine.
Any known leaks with this version ???I think tomcat 5.0 has problems.I have
read issues
it.
I have been re-searching and have read bugs related to memory leaks.Is
there a known bug in the 5 versions of tomcat which leads to a memory
leak??
I have tried various things - nothing seems to work.I tried memory
debugging using Jprobe which does show me that a char[] array size keeps
y to set it to "false" from outside.
>> Initially it's "true".
>>
>> So, i've set it to "false" directly in code,
>> rebuilt tomcat and replaced files
>> ${CATALINA_HOME}/common/lib/jasper-*.jar
>> from production environment
mcat and replaced files ${CATALINA_HOME}/common/lib/jasper-*.jar
> from production environment with fresh ones.
>
> So, it seems that the problem is successfully solved.
> As far as I can see there no more memory leakage.
>
> I think it would be useful to allow users to set proper
no more memory leakage.
I think it would be useful to allow users to set property of
org.apache.jasper.runtime.JspFactoryImpl.USE_POOL from config files or
in any other way, without rebuilding entire tomcat application.
P.S.
In fact, I think, it's not REAL memory leak - memory usage, may be,
will st
Hi Rémy,
It's a very good news for all !!!
Until now, we used a CleanupListener to do such things, and webapps could use
it or not.
Now, Tomcat will do this automatically for us :-))
But I need some complements :
- this new feature will be integrated in Tomcat 3 ? Tomcat 4 ? Tomcat 5.0 ?
- in t
On 11/30/05, Remy Maucherat <[EMAIL PROTECTED]> wrote:
> This issue also affects Hibernate. As it doesn't seem to be a Tomcat
> bug, but would be good to have a fix for, I've added possible
> workarounds for that (reflection code which sets as many static fields
> as possible to null in loaded clas
y application.
>
> After some tests, it turned out that my static fields were not GCed after
> redeploying, getting stuck with the classloader which loaded my classes.
>
> After that, I searched the bugzilla and found
> *Bug# *(Memory Leak in Classloader/Manager deploy/undeplo
Hi, I would like to add my two cents :-)
If I know that a class will only be instantiated once or twice, I
usually prefer to declare the logger field as non-static.
I put in this category Stateless Session EJBs, servlets, filters,
listeners, JSPs, and any singleton classes I implement by myself
-Original Message-
> From: Lionel Farbos [mailto:[EMAIL PROTECTED]
> Sent: 29 November 2005 15:50
> To: Tomcat Users List
> Cc: [EMAIL PROTECTED]
> Subject: Re: Singleton memory leak after redeploying.
>
> On Tue, 29 Nov 2005 09:31:28 +0100
> Mikolaj Rydzewski <
Message-
From: Lionel Farbos [mailto:[EMAIL PROTECTED]
Sent: 29 November 2005 15:50
To: Tomcat Users List
Cc: [EMAIL PROTECTED]
Subject: Re: Singleton memory leak after redeploying.
On Tue, 29 Nov 2005 09:31:28 +0100
Mikolaj Rydzewski <[EMAIL PROTECTED]> wrote:
> Lionel Far
On Tue, 29 Nov 2005 09:31:28 +0100
Mikolaj Rydzewski <[EMAIL PROTECTED]> wrote:
> Lionel Farbos wrote:
>
> >Notes :
> >- Perhaps your Listener will have to delete other objets like SQL drivers,
> >commons logger, ...
> >- see also :
> >http://opensource2.atlassian.com/confluence/spring/pages/vi
On Tue, 29 Nov 2005 00:39:51 -0600
[EMAIL PROTECTED] wrote:
> On Mon, Nov 28, 2005 at 06:24:52PM +0100, Lionel Farbos wrote:
> > Hi Juan,
> >
> > I think your problem can't be solved (only) by Tomcat.
> > The problem is that objets stay in memory because of pointers on static
> > references...
>
Lionel Farbos wrote:
Notes :
- Perhaps your Listener will have to delete other objets like SQL drivers,
commons logger, ...
- see also :
http://opensource2.atlassian.com/confluence/spring/pages/viewpage.action?pageId=2669
Does log4j have some nice method to free all Logger objects? It seems
On Mon, Nov 28, 2005 at 06:24:52PM +0100, Lionel Farbos wrote:
> Hi Juan,
>
> I think your problem can't be solved (only) by Tomcat.
> The problem is that objets stay in memory because of pointers on static
> references...
but aren't those supposed to go away when the classloader is no l
hat my static fields were not GCed after
> redeploying, getting stuck with the classloader which loaded my classes.
>
> After that, I searched the bugzilla and found
> *Bug# *(Memory Leak in Classloader/Manager deploy/undeploy)*:*
> 20758<http://issues.apache.org/bugzilla/show_bug
after
redeploying, getting stuck with the classloader which loaded my classes.
After that, I searched the bugzilla and found
*Bug# *(Memory Leak in Classloader/Manager deploy/undeploy)*:*
20758<http://issues.apache.org/bugzilla/show_bug.cgi?id=20758>
where it says that the bug has been FIXED.
05 9:19 AM
To: users@tomcat.apache.org
Subject: PernGen memory leak with Tomcat 5.5.9
Hi!
We are working on a web application using Struts 1.2.7, deployed on Tomcat
5.5.9 on Solaris SunOS 5.8 and JVM 1.5.0_04-b05 and we have the following
problem:
Sometimes we get an java.lang.OutOfMemoryE
Hi!
We are working on a web application using Struts 1.2.7, deployed on
Tomcat 5.5.9 on Solaris SunOS 5.8 and JVM 1.5.0_04-b05 and we have the
following problem:
Sometimes we get an java.lang.OutOfMemoryError: PermGen space and the
logs do not say anything more about the problem.
We are m
601 - 632 of 632 matches
Mail list logo
