• New Feature
  • Status: Closed
  • 2 Major
  • Resolution: Fixed
  • Console
  • kkannaiy
  • Reporter: gkeim
  • March 26, 2007
  • 0
  • Watchers: 0
  • February 12, 2013
  • April 10, 2007

Description

run-dgc causes distributed garbage collection iff the config has garbage collection disabled and is meant for the operation who wants more control over when dgc happens than that which is provided via the config file. We should provide a way for the operator to force a dgc via the AdminConsole’s Distribubted Garbage Collection page. This would be very easy to do.

Comments

Gary Keim 2007-04-10

Change 2381.

Fiona OShea 2007-05-30

verify that this is resolved. Add a test case as necessary

Kalai Kannaiyan 2007-08-01

Tested with rev 4738, it is working as expected.

  1. Navigate to /install-root folder/samples
  2. modify the tc-config.xml to force the dgc

update under tc-config/servers/server/dso/garbage-collection

false
  1. execute ./start-demo-server.sh -f tc-config.xml
  2. Navigate to install-root folder/samples/pojo
  3. execute ./run.sh &
  4. Launch the admin Console
  5. In the admin Console, select the Garbage collection and click Run GC button

Actual: 2007-08-01 13:56:06,178 [GCRunnerThread] INFO com.tc.management.beans.object.ObjectManagementMonitor - Running GC. 2007-08-01 13:56:06,185 [GCRunnerThread] INFO com.tc.objectserver.api.ObjectManager - Notifying GC : pending = 0 checkedOutCount = 0 2007-08-01 13:56:06,188 [GCRunnerThread] INFO com.tc.management.beans.object.ObjectManagementMonitor - GC finished.