On Mar 7, 2012, at 11:49 AM, Jess Holle wrote:
How can this be a "low" priority JVM bug!?!
I know. My other motive in posting this was to draw attention to it and maybe
get some other folks to vote for it. :-)
On 3/7/2012 11:21 AM, Konstantin Kolinko wrote:
2012/3/7 Kari Scottmailto:kar
How can this be a "low" priority JVM bug!?!
On 3/7/2012 11:21 AM, Konstantin Kolinko wrote:
2012/3/7 Kari Scott:
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:
Objec
2012/3/7 Kari Scott :
>
>
> 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");
> Composite
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)serve
