First failure data capture (FFDC) writes exception summaries and incident files to the profile's ffdc directory. Retention of those files is controlled by the ExceptionFileMaximumAge property, which sets how long an FFDC file may remain before it becomes eligible for purging. The product reads FFDC settings from three separate property files, and each file is consulted at a different point in the server lifecycle. ffdcRun.properties applies while the server is running, ffdcStart.properties applies during startup processing, and ffdcStop.properties applies during shutdown. For the purge policy to behave identically in all three phases, ExceptionFileMaximumAge has to carry the same value in every one of them, which is the position stated in option C.
Options A, B, and D each leave out at least one of the files. Updating only ffdcRun.properties, for example, would change the retention age for a running server but leave startup and shutdown purges operating on the previous value, so files could be removed on an inconsistent schedule or accumulate longer than intended. Option A also refers to "ffdcStart properties" without the .properties extension and names a single file, so it fails on both counts.
The practical rule for administrators is to treat the three files as one logical configuration and edit them together whenever FFDC retention is tuned.
[Reference: First failure data capture (FFDC) property files: ffdcRun.properties, ffdcStart.properties, ffdcStop.properties; Managing FFDC output.]
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit