You'll almost likely find that the reload via Ant does not free up all
resources and so each time you perform a reload you'll be leaking some memory
resulting in OOME after a week.
3 things to do;
Get a profiler to see where you may be losing memory.
Ensure no resource/references are held
I would recommend you upgrade to 5.5.9 if you use struts.
-Original Message-
From: Allistair Crossley [mailto:[EMAIL PROTECTED]
Sent: September 20, 2005 9:56 AM
To: Tomcat Users List
Subject: RE: Out of Memory on Jakarta Tomcat 5.0.19, jdk1.5.0_04
You'll almost likely find
From: Allistair Crossley [mailto:[EMAIL PROTECTED]
Subject: RE: Out of Memory on Jakarta Tomcat 5.0.19, jdk1.5.0_04
3 things to do;
Get a profiler to see where you may be losing memory.
Ensure no resource/references are held onto, dispose
references correctly
Hard restart Tomcat when
On Tuesday 20 September 2005 20:56, Allistair Crossley wrote:
You'll almost likely find that the reload via Ant does not free up all
resources and so each time you perform a reload you'll be leaking some
memory resulting in OOME after a week.
3 things to do;
Get a profiler to see where you
]
Sent: 20 September 2005 15:08
To: Tomcat Users List
Subject: RE: Out of Memory on Jakarta Tomcat 5.0.19, jdk1.5.0_04
From: Allistair Crossley [mailto:[EMAIL PROTECTED]
Subject: RE: Out of Memory on Jakarta Tomcat 5.0.19, jdk1.5.0_04
3 things to do;
Get a profiler to see where
From: NoKideen [mailto:[EMAIL PROTECTED]
usually I use String to collect output first and out.print()
those String
example :
String a=;
a+=Test 1;
a+=Test 2;
// very long , and almost 1 page
out.println(a);
can this cause out of memory problem ?
It won't help much - you'll
2 notes.
When using Java 1.5, StringBuilder class is supposed to be better
according to documentation. Also, what has worked for me, is that if
any of the strings can be generated ahead of time, do so in a static
block and convert the strings to byte[]. This not only eliminates
redundant
I know this problem very well, since I worked on a very memory-consuming
app where I coulnd't even reload twice. It has nothing to do with ant,
and i think I also had such a case with tomcat 5.5 (now working on
normal webapps ;-)
Cautiously, I would never reload via manager (or perhaps once) in
On Tuesday 20 September 2005 21:11, Sonja Löhr wrote:
I know this problem very well, since I worked on a very memory-consuming
app where I coulnd't even reload twice. It has nothing to do with ant,
and i think I also had such a case with tomcat 5.5 (now working on
normal webapps ;-)
what
Unfortunately, I can't give you an answer -
it my well be that my code IS somehow suboptimal, but if the application
runs, all is well, it is just that reload (I'm not sure about start and
stop now) over the manager app.
To be honest, I always waited for the next tomcat release to magically
make
10 matches
Mail list logo
