On 12/06/2012 14:50, Christopher Schultz wrote:
Pid,
On 6/12/12 5:47 AM, Pid wrote:
On 11/06/2012 20:15, Christopher Schultz wrote:
Also, your previously-posted configuration seems a little
insane:
Xms6g -Xmx6g -XX:NewSize=4G -XX:MaxNewSize=4G
-XX:SurvivorRatio=6 -XX:MaxPermSize=512M
On 11/06/2012 20:15, Christopher Schultz wrote:
Jorge,
On 6/11/12 3:01 PM, Jorge Medina wrote:
There is not much running in the machine other than Tomcat. The JVM
actually starts fine, using about 8GB (6GB of heap, + code +
threads etc) but it keeps growing. In about 2 days it runs out of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Pid,
On 6/12/12 5:47 AM, Pid wrote:
On 11/06/2012 20:15, Christopher Schultz wrote:
Also, your previously-posted configuration seems a little
insane:
Xms6g -Xmx6g -XX:NewSize=4G -XX:MaxNewSize=4G
-XX:SurvivorRatio=6 -XX:MaxPermSize=512M
I'm finding it hard to believe, but all points that the problem was
the -Xms option of the Oracle (Sun) JVM.
I originally set it to the same value as -Xmx, so that all memory for
the heap is allocated when the JVM starts.
This works fine in Solaris, but it is not working in Ubuntu.
After removing
I found this interesting article about how Linux handles requests for
memory, look at section 9.6 Overcommit and OOM:
http://www.win.tue.nl/~aeb/linux/lk/lk-9.html
I verified that our system runs with overcommit_memory = 0 and
overcommit_ratio = 50. Which are the default values.
This post suggest
From: Jorge Medina [mailto:cerebrotecnolog...@gmail.com]
Subject: Re: Java process killed by oom-killer in Ubuntu
Nevertheless, I am finding that after removing the -Xms option, the
process memory usage stabilizes and stops growing.
That would seem to indicate that your -Xmx value is simply
[mailto:cerebrotecnolog...@gmail.com]
Subject: Re: Java process killed by oom-killer in Ubuntu
Nevertheless, I am finding that after removing the -Xms option, the
process memory usage stabilizes and stops growing.
That would seem to indicate that your -Xmx value is simply too large for the
system
-enough chunk?
-Jorge
On Mon, Jun 11, 2012 at 11:15 AM, Caldarale, Charles R
chuck.caldar...@unisys.com wrote:
From: Jorge Medina [mailto:cerebrotecnolog...@gmail.com]
Subject: Re: Java process killed by oom-killer in Ubuntu
Nevertheless, I am finding that after removing the -Xms option
From: David kerber [mailto:dcker...@verizon.net]
Subject: Re: Java process killed by oom-killer in Ubuntu
On 6/11/2012 2:30 PM, Jorge Medina wrote:
The machine has 16 GB of memory with no swap space.
The JVM was being started with -Xms and -Xmx equal to 6 GB, so I think
10GB extra would
, Caldarale, Charles R
chuck.caldar...@unisys.com wrote:
From: David kerber [mailto:dcker...@verizon.net]
Subject: Re: Java process killed by oom-killer in Ubuntu
On 6/11/2012 2:30 PM, Jorge Medina wrote:
The machine has 16 GB of memory with no swap space.
The JVM was being started with -Xms
From: Jorge Medina [mailto:cerebrotecnolog...@gmail.com]
Subject: Re: Java process killed by oom-killer in Ubuntu
The JVM actually starts fine, using about 8GB (6GB of heap, + code +
threads etc) but it keeps growing. In about 2 days it runs out of
memory. (The JVM process has reached more
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jorge,
On 6/11/12 3:01 PM, Jorge Medina wrote:
There is not much running in the machine other than Tomcat. The JVM
actually starts fine, using about 8GB (6GB of heap, + code +
threads etc) but it keeps growing. In about 2 days it runs out of
On 7 Jun 2012, at 23:03, Daniel Mikusa dmik...@vmware.com wrote:
- Original Message -
Only 52 java threads. It used to fluctuate more (we made some
changes
to the app to perform a task in a single thread rather than spawning
multiple threads, but the crash still occurs) . The number
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jorge,
On 6/6/12 5:33 PM, Jorge Medina wrote:
The web application uses Spring/Postgres/Mongo.
Are you using MongoDB in-process or anything weird like that? Or are
you connecting through some socket-based (or other) API?
It looks like a memory
It seems my system is running with an relatively old version of the
Tomcat Native Library and old versions of APR and OpenSSL.
Tomcat Native 1.1.19
APR 1.3.8
OpenSSL 0.9.8k
These are the latest versions available:
Tomcat Native 1.1.23
APR 1.4.6
OpenSSL 1.0.1c
I will try disabling the Tomcat
Thanks Martin, but the memory error is not in the Java heap. Basically
my java process keeps growing far beyond the maximum java heap size
allowed.
-Jorge
On Wed, Jun 6, 2012 at 5:57 PM, Martin Gainty mgai...@hotmail.com wrote:
neceista empezar tomcat con JMX por ejemplo:
I am using MongoDB through the Java driver allowing up to 100
connections to the MongoDB server.
I also use DBCP with a max size of 50 JDBC connections.
My webapp uses about 150 JAR files.
There is no native libraries loaded from my webapp as far as I know.
All the app is pure Java code.
- Original Message -
I am using MongoDB through the Java driver allowing up to 100
connections to the MongoDB server.
I also use DBCP with a max size of 50 JDBC connections.
My webapp uses about 150 JAR files.
There is no native libraries loaded from my webapp as far as I know.
All
From: Jorge Medina [mailto:cerebrotecnolog...@gmail.com]
Subject: Re: Java process killed by oom-killer in Ubuntu
Is there a way I can monitor the number of file descriptors in
use by the app?
You can see the open files for any process with lsof:
http://linux.die.net/man/8/lsof
You can
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jorge,
On 6/7/12 3:03 PM, Jorge Medina wrote:
I am using MongoDB through the Java driver allowing up to 100
connections to the MongoDB server.
100 connections sounds a bit high to me, but I don't know your
requirements nor do I know anything
Only 52 java threads. It used to fluctuate more (we made some changes
to the app to perform a task in a single thread rather than spawning
multiple threads, but the crash still occurs) . The number of threads
is always below 100.
jstack -F 21370 | grep ^Thread | wc -l
ps -T -p 21370 (This
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jorge,
On 6/7/12 2:51 PM, Jorge Medina wrote:
It seems my system is running with an relatively old version of
the Tomcat Native Library and old versions of APR and OpenSSL.
Tomcat Native 1.1.19 APR 1.3.8 OpenSSL 0.9.8k
Those aren't terribly
- Original Message -
Only 52 java threads. It used to fluctuate more (we made some
changes
to the app to perform a task in a single thread rather than spawning
multiple threads, but the crash still occurs) . The number of threads
is always below 100.
jstack -F 21370 | grep
23 matches
Mail list logo
