Monitoring JVM Memory and Threads in .NET Applications

Added by Shay Hassidim, last edited by Aleia Hutcherson on May 14, 2008  (view change)
  Search Here
Searching XAP 6.0 Documentation

                                               
Summary: Monitoring JVM memory and threads in .Net Applications, when troubleshooting application memory and thread consumption.

Overview

In some cases, you might want to monitor the activity of the JVM running as part of your .NET application. The jconsole is a great tool that allows you to troubleshoot the JVM internals.

To view and monitor the JVM loaded into the .NET process memory address using jconsole:

  1. Have the following settings as part of your App.config file: 
    <?xml version="1.0" encoding="utf-8" ?>
<configuration>
 <configSections>
  <sectionGroup name="codemesh">
   <sectionGroup name="runtime">
    <section name="Default.Options" type="System.Configuration.NameValueSectionHandler" />
    ...
    
   </sectionGroup>
  </sectionGroup>
 </configSections>
 <codemesh>
  <runtime>
   <Loader name="Default" />
   <Default.Options>
    <add key="com.sun.management.jmxremote.port" value="5144" />
    <add key="com.sun.management.jmxremote.ssl" value="false" />
    <add key="com.sun.management.jmxremote.authenticate" value="false" />
   </Default.Options>
   ...
   
  </runtime>
 </codemesh>
</configuration>
  2. Start jconsole – make sure %JAVA_HOME%\bin is part of your path.
  3. Once the jconsole is started, select the Local tab:



  4. This shows the status of the JVM running in your .NET application:

For more details on JMX and jconsole, refer to:


GigaSpaces 6.0 Documentation Contents (Current Page in Bold)

    Java

    C++

    .NET

    Middleware Capabilities

    Configuration and Management

Add GigaSpaces wiki search to your browser search engines!
(works on Firefox 2 and Internet Explorer 7)

Labels

 
(None)