Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (nike.apache.org: domain of jessh@ptc.com designates
 12.11.148.84 as permitted sender)
Message-ID: <4F579FBE.4050105@ptc.com>
Date: Wed, 07 Mar 2012 11:49:50 -0600
From: Jess Holle <jessh@ptc.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
 rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: Tomcat Users List <users@tomcat.apache.org>
CC: Konstantin Kolinko <knst.kolinko@gmail.com>
Subject: Re: JMX JVM bug workaround question
References: <18040233-D055-4EE4-9AB5-83272F388F09@cdw.com>
 <CABzHfVkfCcOy8t+kG=wDqtAD9v_KTit4E325yHXf6rg0Yyh9MA@mail.gmail.com>
In-Reply-To: 
 <CABzHfVkfCcOy8t+kG=wDqtAD9v_KTit4E325yHXf6rg0Yyh9MA@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

How can this be a "low" priority JVM bug!?!

On 3/7/2012 11:21 AM, Konstantin Kolinko wrote:
> 2012/3/7 Kari Scott<Kari.Scott@cdw.com>:
>>
>> We are using Tomcat 7.0.23 with jdk1.6.0_30 on Solaris 10, mod_ajp 1.3  and Apache 2.2.21.
>>
>> I'm using the following code to retrieve memory information from our JMX server:
>>
>>
>> ObjectName contextObjectName = new ObjectName("java.lang:type=Memory");
>> CompositeData memoryUsage = (CompositeData)server.getAttribute(contextObjectName, "HeapMemoryUsage");
>>
>>
>> This works really well most of the time but we occasionally we get this exception when trying to retrieve HeapMemoryUsage:
>>
>> javax.management.RuntimeMBeanException:
>> java.lang.IllegalArgumentException: committed = 1607688192 should be<  max = 1607270400
>>
>>
>> After some digging, I found that it is a bug in the JVM (It occurs in 1.7, too):
>>
>>   http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=7100266
>>
>>
>> My questions for the list then are has anyone else come across this and, if so, how did you get around it? Is there an alternative way for retrieving used and committed memory from a JMX MBean?
> The issue seems like some threading issue when "max" and "committed"
> memory settings are calculated independently at different moments and
> fail to pass a consistency check between them.
>
> I think I would wait a while and retry, but only once.
>
> Do you check what Runtime.freeMemory(), Runtime.totalMemory() return
> at the same time? Maybe there is so little free memory that it is
> worth to worry.
>
> Best regards,
> Konstantin Kolinko
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org