![]() |
In most problem determination situations, you need to quickly pinpoint the activity log entries related to the problem that you are investigating. One way to do this is to reduce the activity log to a more manageable size. Here are some ways to reduce the size of the activity log:
Setting the size of the activity log
Before starting client or server processes on a host, set the com.ibm.CORBA.activityLogMaxSize runtime property to the desired number of Kbytes. You can use 15K for testing robustness and 50K for long runs.
For more information about specifying runtime properties, see Specifying properties for C++ CORBA clients and servers.
Creating smaller activity logs
Smaller activity logs may speed up your problem determination process. If the run-time error can be reproduced by rerunning your application, consider performing the completing steps to create a set of small activity logs:
You now have a set of small, formatted activity logs. For example, if log2 shows that a client could not find a factory, log1 shows you why that factory was not registered.
Naming formatted logs
Consider giving representative file names for the formatted activity logs; for example, you can specify the following showlog command:
showlogcpp activitycpp.log -d > serverStartup.980808.firstrun.out
Related tasks... | |
Specifying properties for C++ CORBA clients and servers | |
Related concepts... | |
Parent: Problem determination | |
Related reference... | |
Runtime properties for CORBA clients and servers | |