From c23654008b18c4169a3e61149bd3ec46a4af99db Mon Sep 17 00:00:00 2001
From: Geoff Bourne <itzgeoff@gmail.com>
Date: Thu, 8 Jan 2026 18:16:13 -0600
Subject: [PATCH] Leverage ENABLE_ROLLING_LOGS as default for
 GENERATE_LOG4J2_CONFIG (#3860)

---
 scripts/start-finalExec | 6 +-----
 1 file changed, 1 insertion(+), 5 deletions(-)

diff --git a/scripts/start-finalExec b/scripts/start-finalExec
index eb8e1fcb..6c77690f 100755
--- a/scripts/start-finalExec
+++ b/scripts/start-finalExec
@@ -47,7 +47,7 @@ if [ -n "$ICON" ]; then
     fi
 fi
 
-useGeneratedLogs=${GENERATE_LOG4J2_CONFIG:-false}
+useGeneratedLogs=${GENERATE_LOG4J2_CONFIG:-${ENABLE_ROLLING_LOGS:-false}}
 useFallbackJvmFlag=false
 
 SERVER_DIR="$baseDataDir"
@@ -172,10 +172,6 @@ EOF
 
   # Apply the log4j2 configuration
   JVM_OPTS="-Dlog4j.configurationFile=log4j2.xml ${JVM_OPTS}"
-elif isTrue "${ENABLE_ROLLING_LOGS:-false}"; then
-  # Legacy behavior: error if rolling logs explicitly requested but not possible
-  logError "Using rolling logs is currently not possible in the selected version due to CVE-2021-44228"
-  exit 1
 else
   rm -f "${LOGFILE}"
 fi