From dmytro_sheyko at hotmail.com Wed Feb 2 01:34:48 2011 From: dmytro_sheyko at hotmail.com (Dmytro Sheyko) Date: Wed, 2 Feb 2011 16:34:48 +0700 Subject: jmx-dev 6853676: OperatingSystemMXBean.TotalPhysicalMemorySize has incorrect value In-Reply-To: References: Message-ID: Hi, Any updates on it? I don't want to be overly importunate, but the quite trivial fix was available year ago. Maybe I do something wrong, so please suggest what I should do to have this bug fixed. Thanks, Dmytro From: dmytro_sheyko at hotmail.com To: serviceability-dev at openjdk.java.net Subject: 6853676: OperatingSystemMXBean.TotalPhysicalMemorySize has incorrect value Date: Fri, 28 Jan 2011 15:05:45 +0700 Hi, I would like to find sponsor and discuss fix for bug#6853676 OperatingSystemMXBean.TotalPhysicalMemorySize has incorrect value http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6853676 The idea is to use GlobalMemoryStatusEx instead of GlobalMemoryStatus. patch is available here: https://bugs.openjdk.java.net/show_bug.cgi?id=100077 Thanks, Dmytro -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.openjdk.java.net/pipermail/jmx-dev/attachments/20110202/ff8b914c/attachment.html From Alan.Bateman at oracle.com Wed Feb 2 02:05:34 2011 From: Alan.Bateman at oracle.com (Alan Bateman) Date: Wed, 02 Feb 2011 10:05:34 +0000 Subject: jmx-dev 6853676: OperatingSystemMXBean.TotalPhysicalMemorySize has incorrect value In-Reply-To: <4D49281B.3020809@oracle.com> References: <4D49281B.3020809@oracle.com> Message-ID: <4D492C6E.4060308@oracle.com> David Holmes wrote: > Dmytro, > > It looks like this was actually fixed under 6840305 back in July 2009: > > http://hg.openjdk.java.net/jdk7/hotspot-rt/hotspot/rev/8c79517a9300 > > This CR was not updated however. > > Does the problem still exist? > > David Holmes I think this is separate and 6853676 is about com.sun.management.OperatingSystemMXBean. The code for that is in jdk repo in src/windows/native/com/sun/management. It should be using GlobalMemoryStatusEx rather than GlobalMemoryStatus. Dmytro - to your question, serviceability-dev is the right place to bring it. -Alan From David.Holmes at oracle.com Wed Feb 2 01:47:07 2011 From: David.Holmes at oracle.com (David Holmes) Date: Wed, 02 Feb 2011 19:47:07 +1000 Subject: jmx-dev 6853676: OperatingSystemMXBean.TotalPhysicalMemorySize has incorrect value In-Reply-To: References: Message-ID: <4D49281B.3020809@oracle.com> Dmytro, It looks like this was actually fixed under 6840305 back in July 2009: http://hg.openjdk.java.net/jdk7/hotspot-rt/hotspot/rev/8c79517a9300 This CR was not updated however. Does the problem still exist? David Holmes Dmytro Sheyko said the following on 02/02/11 19:34: > Hi, > > Any updates on it? > > I don't want to be overly importunate, but the quite trivial fix was > available year ago. > Maybe I do something wrong, so please suggest what I should do to have > this bug fixed. > > Thanks, > Dmytro > > ------------------------------------------------------------------------ > From: dmytro_sheyko at hotmail.com > To: serviceability-dev at openjdk.java.net > Subject: 6853676: OperatingSystemMXBean.TotalPhysicalMemorySize has > incorrect value > Date: Fri, 28 Jan 2011 15:05:45 +0700 > > Hi, > > I would like to find sponsor and discuss fix for bug#6853676 > OperatingSystemMXBean.TotalPhysicalMemorySize has incorrect value > http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6853676 > > The idea is to use GlobalMemoryStatusEx instead of GlobalMemoryStatus. > > patch is available here: > https://bugs.openjdk.java.net/show_bug.cgi?id=100077 > > Thanks, > Dmytro > From David.Holmes at oracle.com Wed Feb 2 02:09:59 2011 From: David.Holmes at oracle.com (David Holmes) Date: Wed, 02 Feb 2011 20:09:59 +1000 Subject: jmx-dev 6853676: OperatingSystemMXBean.TotalPhysicalMemorySize has incorrect value In-Reply-To: <4D492C6E.4060308@oracle.com> References: <4D49281B.3020809@oracle.com> <4D492C6E.4060308@oracle.com> Message-ID: <4D492D77.5070209@oracle.com> Alan Bateman said the following on 02/02/11 20:05: > David Holmes wrote: >> It looks like this was actually fixed under 6840305 back in July 2009: >> >> http://hg.openjdk.java.net/jdk7/hotspot-rt/hotspot/rev/8c79517a9300 >> >> This CR was not updated however. >> >> Does the problem still exist? >> >> David Holmes > I think this is separate and 6853676 is about > com.sun.management.OperatingSystemMXBean. The code for that is in jdk > repo in src/windows/native/com/sun/management. It should be using > GlobalMemoryStatusEx rather than GlobalMemoryStatus. Thanks Alan, the comments in 6853676 led me astray. As a P4 it looks like this has just slipped through the cracks. David > Dmytro - to your question, serviceability-dev is the right place to > bring it. > > -Alan