-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ozgur,
On 5/17/2010 5:28 AM, Ozgur Ozdemircili wrote:
I have the default server.conf file with :
Connector port=8080 protocol=HTTP/1.1
maxThreads=250
connectionTimeout=2
redirectPort=8443 /
Hi,
I am having a lot of Java Heap OutOfMemory issues. The first change I did
was to add more memory to JVM:
export CATALINA_OPTS=-XX:MaxPermSize=512m -Xms512m -Xmx2048m -server
Yet I have 2 questions
- What are you real life configurations? In a very busy prod environment
what parameters do
On 17/05/2010 09:25, Ozgur Ozdemircili wrote:
Hi,
I am having a lot of Java Heap OutOfMemory issues. The first change I did
was to add more memory to JVM:
export CATALINA_OPTS=-XX:MaxPermSize=512m -Xms512m -Xmx2048m -server
Yet I have 2 questions
- What are you real life
Hi,
-Rhel 5.3 x64
-java version 1.6.0_16
Java(TM) SE Runtime Environment (build 1.6.0_16-b01)
Java HotSpot(TM) 64-Bit Server VM (build 14.2-b01, mixed mode)
-Apache tomcat 6.0.26
-Dual core Intel(R) Xeon(R) CPU E3110 @ 3.00GHz and 4 GB memory each.
Thanks.
Özgür Özdemircili
On 17/05/2010 09:56, Ozgur Ozdemircili wrote:
Hi,
-Rhel 5.3 x64
-java version 1.6.0_16
Java(TM) SE Runtime Environment (build 1.6.0_16-b01)
Java HotSpot(TM) 64-Bit Server VM (build 14.2-b01, mixed mode)
-Apache tomcat 6.0.26
-Dual core Intel(R) Xeon(R) CPU E3110 @ 3.00GHz and 4 GB
Ozgur Ozdemircili wrote:
Hi,
-Rhel 5.3 x64
-java version 1.6.0_16
Java(TM) SE Runtime Environment (build 1.6.0_16-b01)
Java HotSpot(TM) 64-Bit Server VM (build 14.2-b01, mixed mode)
-Apache tomcat 6.0.26
-Dual core Intel(R) Xeon(R) CPU E3110 @ 3.00GHz and 4 GB memory each.
Hè ? do you
On 17/05/2010 10:15, Pid wrote:
On 17/05/2010 09:56, Ozgur Ozdemircili wrote:
Hi,
-Rhel 5.3 x64
-java version 1.6.0_16
Java(TM) SE Runtime Environment (build 1.6.0_16-b01)
Java HotSpot(TM) 64-Bit Server VM (build 14.2-b01, mixed mode)
-Apache tomcat 6.0.26
-Dual core Intel(R) Xeon(R)
Hi,
You could set the one fourth of physical memory size(the
recommended heap size) for -Xms,-Xmx arguments.
What's more, you also analyze the heap using jmap.
Mercy
On 05/17/2010 05:16 PM, André Warnier wrote:
Ozgur Ozdemircili wrote:
Hi,
-Rhel 5.3 x64
-java version 1.6.0_16
Hi,
I have the default server.conf file with :
Connector port=8080 protocol=HTTP/1.1
maxThreads=250
connectionTimeout=2
redirectPort=8443 /
I do not have any Executor.
When I check the manager status in detail I see the threads with ? in front
On 17/05/2010 10:29, Mercy wrote:
Hi,
You could set the one fourth of physical memory size(the recommended
heap size) for -Xms,-Xmx arguments.
Where does this recommendation come from?
It would mean that with 16Gb of RAM one should only use 4Gb for the heap.
p
What's more, you also
Ozgur Ozdemircili wrote:
Hi,
I have the default server.conf file with :
Connector port=8080 protocol=HTTP/1.1
maxThreads=250
connectionTimeout=2
redirectPort=8443 /
I do not have any Executor.
When I check the manager status in detail I see
Hi,
Please take a look at this:
http://java.sun.com/javase/6/docs/technotes/guides/vm/gc-ergonomics.html
*maximum heap size:*
Smaller of 1/4th of the physical memory or 1GB. Before J2SE 5.0, the
default maximum heap size was 64MB. You can override this default
using the |-Xmx|
On 17/05/2010 13:18, Mercy wrote:
Hi,
Please take a look at this:
http://java.sun.com/javase/6/docs/technotes/guides/vm/gc-ergonomics.html
*maximum heap size:*
Smaller of 1/4th of the physical memory or 1GB. Before J2SE 5.0, the
default maximum heap size was 64MB. You can
On 17 May 2010 13:18, Mercy techme...@gmail.com wrote:
Hi,
Please take a look at this:
http://java.sun.com/javase/6/docs/technotes/guides/vm/gc-ergonomics.html
*maximum heap size:*
Smaller of 1/4th of the physical memory or 1GB. Before J2SE 5.0, the
default maximum heap size was
Thank you.
Mercy
On 05/17/2010 08:58 PM, Pid wrote:
On 17/05/2010 13:18, Mercy wrote:
Hi,
Please take a look at this:
http://java.sun.com/javase/6/docs/technotes/guides/vm/gc-ergonomics.html
*maximum heap size:*
Smaller of 1/4th of the physical memory or 1GB. Before J2SE 5.0,
From: André Warnier [mailto:a...@ice-sa.com]
Subject: Re: MaxPermSize / Threads
So, while I am not saying that there are not circumstances where a 2 GB
Heap is justified, it is still a very high number, and maybe you should
have a look at which application really needs so much space
Can you paste the original error from your catalina.out log?
Best
Toni
El 17/05/2010 10:25, Ozgur Ozdemircili escribió:
Hi,
I am having a lot of Java Heap OutOfMemory issues. The first change I did
was to add more memory to JVM:
export CATALINA_OPTS=-XX:MaxPermSize=512m -Xms512m
...@unisys.com
To: users@tomcat.apache.org
Date: Mon, 17 May 2010 08:17:06 -0500
Subject: RE: MaxPermSize / Threads
From: André Warnier [mailto:a...@ice-sa.com]
Subject: Re: MaxPermSize / Threads
So, while I am not saying that there are not circumstances where a 2 GB
Heap is justified
From: Martin Gainty [mailto:mgai...@hotmail.com]
Subject: RE: MaxPermSize / Threads
could you describe compressed object pointers and how implementation
will reduce allocations from JVM heap?thx,
It doesn't reduce the number of allocations, but it does reduce the size of
objects, since
...@unisys.com wrote:
From: André Warnier [mailto:a...@ice-sa.com]
Subject: Re: MaxPermSize / Threads
So, while I am not saying that there are not circumstances where a 2 GB
Heap is justified, it is still a very high number, and maybe you should
have a look at which application really needs so
:
From: André Warnier [mailto:a...@ice-sa.com mailto:a...@ice-sa.com]
Subject: Re: MaxPermSize / Threads
So, while I am not saying that there are not circumstances where a
2 GB
Heap is justified, it is still a very high number, and maybe you
should
have
: MaxPermSize / Threads
So, while I am not saying that there are not circumstances where a
2 GB
Heap is justified, it is still a very high number, and maybe you
should
have a look at which application really needs so much space.
Having an excessively large
From: Ozgur Ozdemircili [mailto:ozgur.ozdemirc...@gmail.com]
Subject: Re: MaxPermSize / Threads
You can see the server giving error every 3-4 minutes until it dies.
By it dies, do you mean you have to restart Tomcat?
Turn on GC logging (-verbose:gc) and use a heap profiler to see if you
]
Subject: Re: MaxPermSize / Threads
You can see the server giving error every 3-4 minutes until it dies.
By it dies, do you mean you have to restart Tomcat?
Turn on GC logging (-verbose:gc) and use a heap profiler to see if
you have a memory leak or simply an undersized heap for the load
24 matches
Mail list logo