WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] Java JVM and memory on Xen

To: "Fajar A. Nugraha" <fajar@xxxxxxxxx>
Subject: Re: [Xen-users] Java JVM and memory on Xen
From: Rob Shepherd <rs@xxxxxxxxxxxxx>
Date: Fri, 13 Nov 2009 20:55:14 +0000
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 13 Nov 2009 12:55:56 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <7207d96f0911101758h31807030m9c9ed937d508d5f2@xxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <4AF97022.7060909@xxxxxxxxxxxxx> <7207d96f0911101758h31807030m9c9ed937d508d5f2@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
Fajar A. Nugraha wrote:
On Tue, Nov 10, 2009 at 8:52 PM, Rob Shepherd <rs@xxxxxxxxxxxxx> wrote:

I finally tracked down the crash to that single 1MB adjustment of RAM.

although the JVM is only configured to use 512MB of RAM MAX (-Xmx512m)

This is very bizarre.  Has anybody seen behaviour before, or have any
comments about why it may be happening?

Java uses MORE memory then what you set on -Xmx. For example, I set
-Xmx512m on an app and "top" shows 693MB RES, 1392M VIRT.

Perhaps you disable swap so that all VIRT needs to be on memory, thus
oom-killer killed it?

I though this earlier but no.
swap total == swap free == 4194296 kB

One would expect an OOM Error to come through a JVM stacktrace. This is a JVM Segfault.

Nevertheless, thank you for your input.

I'd be glad of any further suggestions.

Kind regards

Rob


--
Rob Shepherd BEng PhD - Director / Senior Engineer - DataCymru Ltd



_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users