Reducing file store file sizes
It is possible to reduce the sizes of the log file and store files in the configuration. However, such reduction is only possible when certain conditions are met.
About this task
Reducing the file sizes can be difficult in practice due to the following reasons:
- It is not possible to shrink the files smaller than the amount of space that their contents currently consume.
- There is no support for compaction of the contents of the permanent store file and temporary store file so fragmentation might keep these store files artificially large. As such, when the values of the file sizes in the configuration are reduced and the messaging engine restarted, it might not be possible to change the sizes of the files to the required values.
When this situation occurs, the messaging engine emits warning
messages to SystemOut.log and continues to use the
existing values. It attempts to apply the configuration changes repeatedly
each time it starts until it succeeds.
Note: 這個主題參照一或多個應用程式伺服器日誌檔。
此外,在分散式和 IBM® i 系統上,另外也建議您可以配置伺服器來使用「高效能可延伸記載 (HPEL)」日誌和追蹤基礎架構,而不使用 SystemOut.log、SystemErr.log, trace.log 及 activity.log 檔案。HPEL 與原生 z/OS® 記載機能也可以一起使用。如果您使用 HPEL,則可以從伺服器設定檔 bin 目錄,利用 LogViewer 指令行工具來存取您所有的日誌和追蹤資訊。請參閱有關利用 HPEL 疑難排解應用程式的資訊,以取得更多使用 HPEL 的相關資訊。
Problems might also arise when the file store file sizes are set too small.