You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* fix log4j config logic to not break when not using json; remove commented out legacy logging options from application.properties; bump to v26.2
* remove rest of legacy logging options from application.properties
# below assumes using local log4j2.xml file, as the embedded version is not available for edits until after server is running
@@ -226,20 +225,22 @@ main() {
226
225
227
226
sed -i "s/@@encryptionKey@@/${LABKEY_EK}/" config/application.properties
228
227
229
-
# Check if we want JSON output, we are using the base log4j2.xml config
228
+
# Check if we want JSON output, and/or if we are using the base log4j2.xml config
229
+
export LOG4J_CONFIG_OPTION=""
230
230
if [ "${JSON_OUTPUT}"="true" ] && [ "${LOG4J_CONFIG_FILE}"="log4j2.xml" ];then
231
231
echo"JSON_OUTPUT==true && LOG4J_CONFIG_FILE==log4j2.xml, so using the base log4j2.xml with labkey.log4j2.xml overrides, to send JSON output to console"
# if the override file exists and isn't empty, use that to override whatever was set in LOG4J_CONFIG_FILE (which might still be server default of log4j2.xml)
echo"saw JSON_OUTPUT=$JSON_OUTPUT and LOG4J_CONFIG_FILE=$LOG4J_CONFIG_FILE and LOG4J_CONFIG_OVERRIDE=$LOG4J_CONFIG_OVERRIDE (which, if defined, was empty)"
239
+
echo"... so configuring nothing for LOG4J_CONFIG_OPTION"
0 commit comments