Hi,
I was having some problems with perm gen space on one of our tomcat
instances and decided to increase the perm gen size and review the
JAVA_OPTS settings in general when I noticed something curious. No
settings are currently made so its just running with default values, but
the manager
maybe the value for environment variables called JAVA_OPTS equals those
values ?
try to echo $JAVA_OPTS and see if theres any value.
On 10/13/06, Alan Flisch [EMAIL PROTECTED] wrote:
Hi,
I was having some problems with perm gen space on one of our tomcat
instances and decided to increase
Already checked that, it's not in the environment and not set in either
startup.sh or catalina.sh.
On Fri, 2006-10-13 at 14:17 +0700, Lintang JP wrote:
maybe the value for environment variables called JAVA_OPTS equals those
values ?
try to echo $JAVA_OPTS and see if theres any value.
On
/etc/init.d/tomcat5 ?
Check for -Xms and -Xmm options
On 10/13/06, Alan Flisch [EMAIL PROTECTED] wrote:
Already checked that, it's not in the environment and not set in either
startup.sh or catalina.sh.
On Fri, 2006-10-13 at 14:17 +0700, Lintang JP wrote:
maybe the value for environment
Good idea, but nothing set there either. The fact it's such an odd
number is another perplexing issue.
On Fri, 2006-10-13 at 09:36 +0200, Pascal Alberty wrote:
/etc/init.d/tomcat5 ?
Check for -Xms and -Xmm options
On 10/13/06, Alan Flisch [EMAIL PROTECTED] wrote:
Already checked that,
Thanks, I suspected that, but couldn't find a reference in any JVM docs.
Do you have a reference I could look at so I could better understand
what is going on?
In order for me to set an appropriate larger perm gen size, I suppose
I'd need to know what it currently is. I seem to remember it is
def perm size is 64Mb
On 10/13/06, Alan Flisch [EMAIL PROTECTED] wrote:
Thanks, I suspected that, but couldn't find a reference in any JVM docs.
Do you have a reference I could look at so I could better understand
what is going on?
In order for me to set an appropriate larger perm gen size, I
Thanks. Found a reference too:
http://java.sun.com/j2se/1.5.0/docs/guide/vm/gc-ergonomics.html
Going to set the following...
-server
-Xmx2000m
-XX:MaxPermSize=256m
On Fri, 2006-10-13 at 12:38 +0200, Leon Rosenberg wrote:
def perm size is 64Mb
On 10/13/06, Alan Flisch [EMAIL PROTECTED]
just as note Xmx2000m works on 64bit vm only
and you can use g instead of 1000m - -Xmx2g
regards
Leon
P.S. You should set your ms=mx, saves time :-)
On 10/13/06, Alan Flisch [EMAIL PROTECTED] wrote:
Thanks. Found a reference too:
I thought you were safe up to 4000m (in practice a little lower) for the
32 bit VM.
Regards,
Alan
On Fri, 2006-10-13 at 13:04 +0200, Leon Rosenberg wrote:
just as note Xmx2000m works on 64bit vm only
and you can use g instead of 1000m - -Xmx2g
regards
Leon
P.S. You should set your
Nope - the 32Bit JVM can only deal with about 1.5GB Ram
Andrew
On 13/10/2006, at 2:51 PM, Alan Flisch wrote:
I thought you were safe up to 4000m (in practice a little lower)
for the
32 bit VM.
Regards,
Alan
-
To start
Leon,
The default memory values depends on your machine (processor speed and
count, total amount of memory) and are guessed by the vm (if not
explicitely specified) upon application start.
Times of 64Mb max memory are long over now.
Really? Seems like 32-bit Sun JVM on Sparc has exactly 64MB
Hmm,
I'm not familiar with limitations on solaris. On linux 32bit VM can
allocate 1.6-1.8 GB depending on vendor (1.6 for sun-jdk).
On the other side, if you are on 64bit OS (and you probably are, or
how could you adress 16GB otherwise), why not using 64bit jdk?
regards
Leon
On 10/13/06, Alan
Christopher,
unfortunately google is not your friend in this case and the document
seems outdated :-)
http://java.sun.com/docs/hotspot/gc5.0/ergo5.html
n the J2SE platform version 5.0 a class of machine referred to as a
server-class machine has been defined as a machine with
2 or more
It could actually be a 64 bit JVM (I didn't install it) although I
suspect not, but as I have no need to push the memory up any further
just now, I'll leave addressing that till later.
I'll maybe just make it 1600m or something for now as that should be
more than adequate. The server isn't
From: Andrew Miehs [mailto:[EMAIL PROTECTED]
Subject: Re: Max Memory Reading
Nope - the 32Bit JVM can only deal with about 1.5GB Ram
That's a Windows, not JVM, limitation. The virtual memory setup is
different on Solaris, so higher values are possible.
- Chuck
THIS COMMUNICATION MAY
From: Alan Flisch [mailto:[EMAIL PROTECTED]
Subject: Re: Max Memory Reading
I thought you were safe up to 4000m (in practice a little
lower) for the 32 bit VM.
Depends on the OS. For Windows, the limit is around 1.5 - 1.6 GB, since
the JVM code, heap, several ancilliary DLLs, and other
From: Leon Rosenberg [mailto:[EMAIL PROTECTED]
Subject: Re: Max Memory Reading
On the other side, if you are on 64bit OS (and you probably are, or
how could you adress 16GB otherwise), why not using 64bit jdk?
Did Solaris 5.9 have a 64-bit version? It's a bit on the old side, so I
doubt
From: Leon Rosenberg [mailto:[EMAIL PROTECTED]
Subject: Re: Max Memory Reading
unfortunately google is not your friend in this case and the document
seems outdated :-)
http://java.sun.com/docs/hotspot/gc5.0/ergo5.html
Why do you think it's outdated? What's described is what the current
:
From: Leon Rosenberg [mailto:[EMAIL PROTECTED]
Subject: Re: Max Memory Reading
unfortunately google is not your friend in this case and the document
seems outdated :-)
http://java.sun.com/docs/hotspot/gc5.0/ergo5.html
Why do you think it's outdated? What's described is what
From: Alan Flisch [mailto:[EMAIL PROTECTED]
Subject: RE: Max Memory Reading
It seems to be contradicted by this document
http://java.sun.com/j2se/1.5.0/docs/guide/vm/gc-ergonomics.html and by
my experience of seeing a near 1GB heap with no -Xmx option set
anywhere.
Maybe I'm confused
, Caldarale, Charles R wrote:
From: Alan Flisch [mailto:[EMAIL PROTECTED]
Subject: RE: Max Memory Reading
It seems to be contradicted by this document
http://java.sun.com/j2se/1.5.0/docs/guide/vm/gc-ergonomics.html and by
my experience of seeing a near 1GB heap with no -Xmx option set
Memory Reading
It seems to be contradicted by this document
http://java.sun.com/j2se/1.5.0/docs/guide/vm/gc-ergonomics.html and by
my experience of seeing a near 1GB heap with no -Xmx option set
anywhere.
Maybe I'm confused by which doc Leon thought was outdated (the perils of
doing top
: Max Memory Reading
Nope - the 32Bit JVM can only deal with about 1.5GB Ram
That's a Windows, not JVM, limitation. The virtual memory setup is
different on Solaris, so higher values are possible.
- Chuck
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
MATERIAL
From: joon yoo [mailto:[EMAIL PROTECTED]
Subject: Re: Max Memory Reading
is it a windows limitation or an intel x86 limitation?
Windows, due to limiting an individual process' virtual space to 2 GB.
(Some versions of Windows Server allow configuration of a 3 GB process
space
25 matches
Mail list logo
