FROM <http://www-1.ibm.com/support/docview.wss?rs=693&context=SSBTEG&dc=DA490&dc=DA4A10&dc=DB520&dc=DA4A30&dc=DB530&dc=DA480&dc=D700&dc=DA4A20&dc=DB560&dc=DA440&dc=DA460&dc=DA430&dc=DA470&dc=DB550&dc=D600&dc=DB600&dc=DA420&dc=DA500&dc=DA410&dc=DB540&dc=DB700&dc=DA400&dc=DB510&uid=swg21239674&loc=en_US&cs=utf-8&lang=en>

Problem

Garbage Collection (GC) logs are huge and cannot be contained in a single file or takes up too much space.

Cause

Space and file size constraints, especially in production environments can be a good reason to start using circular logging.

Solution

The format is as follows: -Xverbosegclog:[DIR_PATH][FILE_NAME]#,X,Y For example: -Xverbosegclog:/usr/eai/IBM/orb#.log,5,2 The above example generates 5 files in /usr/eai/IBM path under the names orbtrc1.log, orbtrc2.log, etc up to orbtrc5.log, each containing 2 GC occurrences.