Repeated Redeployment of Exploded WAR Files Due to Runtime File Modifications

[parmarshivender]

Description: We are encountering an issue where Open Liberty continuously redeploys exploded WAR files due to runtime changes in certain files. Specifically, files such as log files, mv.db (database), and .xml configuration files are modified at runtime, and Open Liberty treats these changes as a reason to redeploy the exploded WAR. This leads to unnecessary redeployments, affecting server stability and performance.

We have identified two main concerns:

1. Exclusion of Modified Runtime Files: Is there any configuration or mechanism in Open Liberty to exclude specific runtime-modified files from triggering redeployment? For example, we want to exclude certain log files, database files (e.g., mv.db), and configuration files that are frequently updated at runtime but should not be treated as deployment changes.

2. Custom Log File Location: Additionally, is there a recommended way to configure Open Liberty to write logs to a different directory, outside the exploded WAR folder? This would allow us to ensure that log file changes do not impact the redeployment process. We are looking for a configuration that would allow us to move log files and other runtime files to a safe location, separate from the deployment artifacts.

Conclusion: These issues are causing performance degradation in our environment, where repeated redeployment is causing instability. We would appreciate guidance or a new feature that addresses the exclusion of specific files from redeployment triggers and the ability to specify an alternate location for logs and other runtime files.

Thank you for your attention to this matter.