Resolution:
Description:
=========
When using TIBCO Kabira products you may remark on some cases that the log file named coordinator.stdout has a large size and that there is no rollover done for this file.

Environment/Product version:
=========================
Solaris / Linux:
P.KPSA, P.KTP, P.KxDR (all versions)


Symptoms:
========
Large size of log file named coordinator.stdout.

Cause:
=====
The large size of this file could be explained by:

1). Use of "printf" operation on custom source code.
2). Uncatched exception on the custom source code.

Resolution:
==========
There is no way to control the size of the coordinator.stdout file. The standard output is just redirected to this file.  What you could see there is what is supposed to go to the console. In order to avoid such a case, instead of "printf" operation, even for debugging during the  development period, the defaults "log services" tools must be used. Also make sure that you catch all exceptions on your custom user source code.

If your application has been running for an extensive time period, you can archive this file while doing the following operations:

// save this log file content
# cp coordinator.stdout $MyArchiveDir

// refresh file content since there
#cat /dev/null > coordinator.stdout