In most problem determination situations, you need to quickly pinpoint the message log entries related to the problem that you are investigating. One way to do this is to reduce the message log to a more manageable size by setting its size, or by creating smaller messages logs.
Setting the size of the message log
Before starting client or server processes on a host, set the com.ibm.CORBA.logger.maxLogFileSize run-time property to the desired number of kilobytes. For more information about specifying run-time properties, see "Specifying run-time properties for CORBA C++ clients and servers".
Creating smaller message logs
Smaller message logs can speed upyour problem determination process. If the run-time error can be reproduced by rerunning your application, consider performing the following steps to create a set of small message logs:
This ensures that you start your problem diagnosis with an empty message log, which minimizes the amount of extraneous information that you need to consider when diagnosing problems.
This allows you to keep the server initialization messages together in a small message log.
This message log contains messages that directly relate to the test run.
You now have a set of message logs that are small enough to be manageable and useful for comparison. For example, if testrun.log shows that a client could not find a factory, then serverinit.log might show you why that factory was not registered.