RMI gcInterval - Does it invoke a Full GC?

Question

My query is with regard to the bug reported here: [http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6200091]
The Bug description suggests that if the rmi gc interval is left at its default value of 1 minute (for JDK 1.5) it causes a Full Garbage Collection (and not a minor GC) cycle to trigger every minute.
Q: Is this understanding correct?
If the answer to the above is 'Yes', then,
Q: Does the full GC triggered whenever the 'sun.rmi.dgc.server.gcInterval'  elapses cause a full GC on the full JVM heap on the server and also have a FULL GC logged in the catalina.out (if running on Tomcat servlet container) similar to the following? I know the answer to this would be Yes! but I just want to be 200% sure!
[Full GC 36242.268: [Tenured: 284568K->284877K(1864192K), 1.9276716 secs] 307279K->284877K(2090304K), [Perm : 61047K->61047K(61184K)], 1.9280748 secs]Obviously assume that the following specifc JVM arguments in place:
-XX:+PrintGCTimeStamps
-XX:+PrintGCApplicationConcurrentTime
-XX:+PrintGCApplicationStoppedTime
-XX:+PrintGCDetails
-XX:+PrintTenuringDistribution

Answer 1

The following information in the document present here http://docs.sun.com/app/docs/doc/820-4289/abeia?a=view answers my original question!
+The Communications Server uses RMI in the Administration module for monitoring. Garbage cannot be collected in RMI-based distributed applications without occasional local collections, so RMI forces a periodic full collection. Control the frequency of these collections with the property -sun.rmi.dgc.client.gcInterval. For example, - java -Dsun.rmi.dgc.client.gcInterval=3600000 specifies explicit collection once per hour instead of the default rate of once per minute.+
However, this means we are observing anomalous behaviour in our application. The GC logs indicate that FULL GC cycles are NOT happening. Following is what I see in the GC logs when I grep for Full GC
16.892: [Full GC 16.892: [Tenured: 2827K->10193K(1864192K), 0.2641562 secs] 98121K->10193K(2090304K), [Perm : 20479K->20479K(20480K)], 0.2643126 secs]
26.174: [Full GC 26.174: [Tenured: 10193K->12032K(1864192K), 0.2939796 secs] 115023K->12032K(2090304K), [Perm : 24576K->24576K(24576K)], 0.2941415 secs]
31.949: [Full GC 31.949: [Tenured: 12032K->17890K(1864192K), 0.3886069 secs] 185492K->17890K(2090304K), [Perm : 28671K->28671K(28672K)], 0.3887846 secs]
38.411: [Full GC 38.411: [Tenured: 17890K->22908K(1864192K), 0.4984410 secs] 180429K->22908K(2090304K), [Perm : 32768K->32439K(32768K)], 0.4986871 secs]
332.245: [Full GC 332.246: [Tenured[Unloading class sun.reflect.GeneratedMethodAccessor100]
4110.831: [Full GC 4110.831: [Tenured[Unloading class sun.reflect.GeneratedMethodAccessor37]
13818.482: [Full GC 13818.482: [Tenured: 151201K->106589K(1864192K), 1.0052010 secs] 336363K->106589K(2090304K), [Perm : 44799K->44799K(44800K)], 1.0054616 secs]
17622.990: [Full GC 17622.990: [Tenured[Unloading class sun.reflect.GeneratedConstructorAccessor83]The time stamps indicate that Full GC cycles are not happening every minute as per the default value of sun.rmi.dgc.server.gcInterval. I have not changed sun.rmi.dgc.server.gcInterval from its default value (i.e. I have not added an explicit JVM argument to change it from its default value on 1 minute)
Can someone explain why am I not seeing Full GC cycles every minute as expected?
System Properties
Platform: Solaris 10
JDK: 1.5.0_14
Tomcat 5.5.27
Apache 2.2.9