Databases
StackOverflow2013
Postsdbo
POPotential Memory Leak in rmi
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POPotential Memory Leak in rmi
    primarykey
    data
    text
    <p>We have a service that is being monitored via JMX. The JVM heap usage is growing and even major collections are not able to remove the garbage. Inspecting the heap shows garbage consisting of RMI related references (mostly, if not all, related class loaders). The only way to alleviate the issue is to issue explicit gc call through JMX (that removes all accumulated garbage). Our gc related options are:</p> <pre><code>-XX:+UseParNewGC -XX:+UseConcMarkSweepGC -XX:+CMSParallelRemarkEnabled -XX:SurvivorRatio=8 -XX:MaxTenuringThreshold=1 -XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly </code></pre> <p>And we have not touched either of: DisableExplicitGC or sun.rmi.dgc.server.gcInterval</p> <p>I believe the problem is supposed to addressed by the code in sun.misc.GC.Daemon:</p> <pre><code>public void run() { for (;;) { long l; synchronized (lock) { l = latencyTarget; if (l == NO_TARGET) { /* No latency target, so exit */ GC.daemon = null; return; } long d = maxObjectInspectionAge(); if (d &gt;= l) { /* Do a full collection. There is a remote possibility * that a full collection will occurr between the time * we sample the inspection age and the time the GC * actually starts, but this is sufficiently unlikely * that it doesn't seem worth the more expensive JVM * interface that would be required. */ System.gc(); d = 0; } /* Wait for the latency period to expire, * or for notification that the period has changed */ try { lock.wait(l - d); } catch (InterruptedException x) { continue; } } } } </code></pre> <p>For some reason the above System.gc is not being invoked (that has been verified by looking at gc logs). Anyone has a suggestion as to how to address the issue?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USsmerny
    1. USLev
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. POPotential Memory Leak in rmi
      1. USLee Mighdoll
      1. VTFavorite
    1. CODid you ever get OutOfMemoryError?
      singulars
      1. POPotential Memory Leak in rmi
      1. USnullptr
    2. COI strongly suspect you might not be closing connections/sockets properly.
      singulars
      1. POPotential Memory Leak in rmi
      1. USkosa
    3. CO@Nambari There are no connections to close in RMI or JMX. What are you talking about?
      singulars
      1. POPotential Memory Leak in rmi
      1. USuser207421
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload