Endre Stølsvik wrote:
Why not? I don't think this is correct. See, if the class isn't referenced
anymore, by not having any referenced objects of that class (by any
reference), nor having the class object referenced, on the stack of any of
the JVM's created Threads, then the static fields of that
On Wed, 16 Jun 2004, Shapira, Yoav wrote:
|
| Hola ;)
|
| Okay? Expected? I don't get that. Can you point me to a email-subject
| of
| one of those threads? Or several?!
|
| There are a number of issues in this space. For example, if your
| servlet class keep a static reference, that can't be
On Tue, 15 Jun 2004, Shapira, Yoav wrote:
|
| Hola,
Yo!
|
| I know - but Sun's VMs surely seems to follow your suggestions!
|
| They might, and they might not, that's the point. Other VM
| implementations can choose to ignore System.gc(), or even Sun
| implementations on certain platforms
Hola ;)
Okay? Expected? I don't get that. Can you point me to a email-subject
of
one of those threads? Or several?!
There are a number of issues in this space. For example, if your
servlet class keep a static reference, that can't be garbage collected
when the webapp is recycled. Therefore
this might be a bit off topic, but if you want to profile your app in tomcat, Sun
Research has an experimental VM called JFluid. http://research.sun.com/projects/jfluid/
it is basically the jdk1.4.2_03 vm with hooks for profiling. it might help track down
GC and memory issues for those who
On Mon, 14 Jun 2004, Woodchuck wrote:
| Runtime.getRuntime().maxMemory() will get you the
| maximum amount of memory for your jvm.
Yeah, check out maxMem, freeMem and totalMem.. Are those something along
the line of what you're looking for?
Endre
On Tue, 15 Jun 2004, Endre Stølsvik wrote:
| On Mon, 14 Jun 2004, Woodchuck wrote:
|
| | Runtime.getRuntime().maxMemory() will get you the
| | maximum amount of memory for your jvm.
|
| Yeah, check out maxMem, freeMem and totalMem.. Are those something along
| the line of what you're looking for?
Hi,
You might also want to try .gc() (force Garbage Collection) - run
freeMemory() right before and right after .gc(), print out the diff
too.
Man, I expect this error from novice posters, but not from you ;)
System.gc is ONLY A SUGGESTION. The more recent the JVM, the more
likely it is to be
On Tue, 15 Jun 2004, Shapira, Yoav wrote:
|
| Hi,
|
| You might also want to try .gc() (force Garbage Collection) - run
| freeMemory() right before and right after .gc(), print out the diff
| too.
|
| Man, I expect this error from novice posters, but not from you ;)
Oh, thanks..! ;)
| System.gc
Hola,
I know - but Sun's VMs surely seems to follow your suggestions!
They might, and they might not, that's the point. Other VM
implementations can choose to ignore System.gc(), or even Sun
implementations on certain platforms (many J2ME installations ignore
these calls).
Well, 1.5beta2
:[EMAIL PROTECTED]
Sent: 10 June 2004 03:15
To: Tomcat Users List
Subject: RE: Memory Settings On Tomcat
by the way, in case you haven't heard of it,
http://mc4j.sourceforge.net/
mc4J can monitor tomcat4 and generate nice graphs. I
haven't used it, but it looks nice.
peter
--- Michael Duffy
I wish I could help you here, but I haven't used it. I know some people on the mailing
list have. Hopefully one of them will respond. You probably should post a message to
MC4J mailing list for asssitance.
peter
Dale, Matt [EMAIL PROTECTED] wrote:Hi,
I downloaded this and it seems to have
Runtime.getRuntime().maxMemory() will get you the
maximum amount of memory for your jvm.
--- Dale, Matt [EMAIL PROTECTED] wrote:
Hi,
I downloaded this and it seems to have potential.
Unfortunately I cant work out where to get the heap
sizing information which is one of the more
important
of parameters to
span
this
space? Thanks - %
--- Shapira, Yoav wrote:
Hi,
I've got Tomcat 4.1.29 installed to run as a
service
under JDK 1.4.1_05 on this Windows 2000
server.
The
Tomcat memory settings on startup are -Xms64m
and
-Xmx1024m
I recently had a problem with a Windoze server hanging
up due to memory problems.
I've got Tomcat 4.1.29 installed to run as a service
under JDK 1.4.1_05 on this Windows 2000 server. The
Tomcat memory settings on startup are -Xms64m and
-Xmx1024m. The server has 512MB of physical RAM
installed
Hi,
I've got Tomcat 4.1.29 installed to run as a service
under JDK 1.4.1_05 on this Windows 2000 server. The
Tomcat memory settings on startup are -Xms64m and
-Xmx1024m. The server has 512MB of physical RAM
It's not a good idea to set -Xmx to a higher amount than the amount of
physical RAM
installed to run as a service
under JDK 1.4.1_05 on this Windows 2000 server. The
Tomcat memory settings on startup are -Xms64m and
-Xmx1024m. The server has 512MB of physical RAM
installed. The Windoze task manager says Tomcat is
sitting at ~128MB of memory.
My understanding is that Java's
on this Windows 2000 server. The
Tomcat memory settings on startup are -Xms64m and
-Xmx1024m. The server has 512MB of physical RAM
It's not a good idea to set -Xmx to a higher amount
than the amount of
physical RAM: the JVM will thrash once it reaches
much less than 512MB.
My understanding
PROTECTED] wrote:I recently
had a problem with a Windoze server hanging
up due to memory problems.
I've got Tomcat 4.1.29 installed to run as a service
under JDK 1.4.1_05 on this Windows 2000 server. The
Tomcat memory settings on startup are -Xms64m and
-Xmx1024m. The server has 512MB
2000 server. The
Tomcat memory settings on startup are -Xms64m and
-Xmx1024m. The server has 512MB of physical RAM
installed. The Windoze task manager says Tomcat is
sitting at ~128MB of memory.
My understanding is that Java's garbage collection
will reclaim heap-allocated memory to the JVM
hope that helps.
peter
Michael Duffy wrote:I recently
had a problem with a Windoze server hanging
up due to memory problems.
I've got Tomcat 4.1.29 installed to run as a service
under JDK 1.4.1_05 on this Windows 2000 server. The
Tomcat memory settings on startup are -Xms64m
/serverinfo
/manager/jmxproxy
etc.
http://jakarta.apache.org/tomcat/tomcat-5.0-doc/manager-howto.html
Thanks,
-Dave
-Original Message-
From: Peter Lin [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 09, 2004 8:12 AM
To: Tomcat Users List
Subject: Re: Memory Settings On Tomcat
if you can
/manager/serverinfo
/manager/jmxproxy
etc.
http://jakarta.apache.org/tomcat/tomcat-5.0-doc/manager-howto.html
Thanks,
-Dave
-Original Message-
From: Peter Lin [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 09, 2004 8:12 AM
To: Tomcat Users List
Subject: Re: Memory Settings On Tomcat
if you
Tomcat 4.1.29 installed to run as a
service
under JDK 1.4.1_05 on this Windows 2000 server. The
Tomcat memory settings on startup are -Xms64m and
-Xmx1024m. The server has 512MB of physical RAM
It's not a good idea to set -Xmx to a higher amount
than the amount of
physical RAM: the JVM
to run as a
service
under JDK 1.4.1_05 on this Windows 2000 server. The
Tomcat memory settings on startup are -Xms64m and
-Xmx1024m. The server has 512MB of physical RAM
It's not a good idea to set -Xmx to a higher amount
than the amount of
physical RAM: the JVM will thrash once it reaches
much
as a
service
under JDK 1.4.1_05 on this Windows 2000 server.
The
Tomcat memory settings on startup are -Xms64m and
-Xmx1024m. The server has 512MB of physical RAM
It's not a good idea to set -Xmx to a higher
amount
than the amount of
physical RAM: the JVM will thrash once it reaches
much
under JDK 1.4.1_05 on this Windows 2000 server.
The
Tomcat memory settings on startup are -Xms64m
and
-Xmx1024m. The server has 512MB of physical RAM
It's not a good idea to set -Xmx to a higher
amount
than the amount of
physical RAM: the JVM will thrash once it
reaches
much
27 matches
Mail list logo
