To: [EMAIL PROTECTED]
Subject: Re: out of memory problem. Help!
Remy Maucherat wrote:
This is not true: there's indeed a memory leak with 5.0.16, but it would
occur only with specific traffic patterns. It will not bring a server
down in just a few requests.
Indeed. The thread
[mailto:[EMAIL PROTECTED]
Sent: Friday, January 16, 2004 9:19 PM
To: Tomcat Users List
Subject: Re: out of memory problem. Help!
Shapira, Yoav wrote:
Howdy,
root cause
java.lang.OutOfMemoryError
It happens When the corresponding request returns more than
2-3
rows from
attention.
[EMAIL PROTECTED] 01/19/04 01:20AM
Check session-timeout in web.xml. -1 is never timeout
session-timeout-1/session-timeout
-Original Message- From: Christophe Andreoli
[mailto:[EMAIL PROTECTED] Sent: Friday, January 16, 2004 9:19 PM To:
Tomcat Users List Subject: Re: out of memory
to be a binary
download yet
Cheers ADC
-Original Message-
From: David Strupl [mailto:[EMAIL PROTECTED]
Sent: 19 January 2004 17:00
To: [EMAIL PROTECTED]
Subject: Re: out of memory problem. Help!
If you use tomcat 5.0.x upgrade to 5.0.18. If you use 4.1.x downgrade to
4.1.27
download yet
Cheers ADC
-Original Message- From: David Strupl
[mailto:[EMAIL PROTECTED] Sent: 19 January 2004 17:00 To:
[EMAIL PROTECTED] Subject: Re: out of memory problem.
Help!
If you use tomcat 5.0.x upgrade to 5.0.18. If you use 4.1.x downgrade
to 4.1.27. There is a significant memory
...does not seem to be a binary download yet
I suggest you continue investigating with your profiler: you have a
different problem.
-Original Message- From: David Strupl
[mailto:[EMAIL PROTECTED] Sent: 19 January 2004 17:00 To:
[EMAIL PROTECTED] Subject: Re: out of memory problem.
Help
Remy Maucherat wrote:
This is not true: there's indeed a memory leak with 5.0.16, but it would
occur only with specific traffic patterns. It will not bring a server
down in just a few requests.
Indeed. The thread pool has to grow and shrink for this to happen.
Unfortunatelly quite common e.g. day
set maxSpareThreads=minSpareThreads=maxThreads will cause the system to
never shrink the pool
Filip
-Original Message-
From: news [mailto:[EMAIL PROTECTED] Behalf Of David Strupl
Sent: Monday, January 19, 2004 9:58 AM
To: [EMAIL PROTECTED]
Subject: Re: out of memory problem. Help!
Remy
: Re: out of memory problem. Help!
Remy Maucherat wrote:
This is not true: there's indeed a memory leak with 5.0.16, but it would
occur only with specific traffic patterns. It will not bring a server
down in just a few requests.
Indeed. The thread pool has to grow and shrink for this to happen
Check session-timeout in web.xml.
-1 is never timeout
session-timeout-1/session-timeout
-Original Message-
From: Christophe Andreoli [mailto:[EMAIL PROTECTED]
Sent: Friday, January 16, 2004 9:19 PM
To: Tomcat Users List
Subject: Re: out of memory problem. Help!
Shapira, Yoav wrote
- Get more memory
- allocate more memory to the JVM
(http://jakarta.apache.org/tomcat/faq/memory.html#adjust)
- Don't place 20,000 ros of data in memory
- Limit the size of your query
-Tim
Christophe Andreoli wrote:
Hello !
I have a Struts/jsp Application
Ich get an out of memory
Howdy,
root cause
java.lang.OutOfMemoryError
It happens When the corresponding request returns more than 2-3
rows from the database, not every time
Perhaps you should allocate your JVM more memory, by using the Java -Xmx
parameter. Alternatively, consider a system design that
Shapira, Yoav wrote:
Howdy,
root cause
java.lang.OutOfMemoryError
It happens When the corresponding request returns more than 2-3
rows from the database, not every time
Perhaps you should allocate your JVM more memory, by using the Java -Xmx
parameter.
I did it and I
Howdy,
It works better but why are the 2000 objects are not garbaged after
each
request ?
There's only one reason objects aren't garbage-collected in java: other
objects are keeping references to them. You can inspect or profile your
code to see what keeps references to what.
Yoav Shapira
14 matches
Mail list logo
