In a clustered environment, log level changes may not be reflected

Please be aware that the page you are viewing has been machine translated from Japanese into English and may contain some translation errors. If you observe any issues with the translation, please contact us.

event

• cluster environment.
• When the log level was changed from Control Panel > Server Administration > Log Levels, the logs were not output.
• The log level you set may change each time you access the site.

Environment

• DXP 7.0+

solution

• The fact that the settings appeared to be different for each access may be due to the fact that the nodes to be accessed were sorted by the load balancer.
  It is also possible that some tasks are executed only on the Master node, so that operations in categories set to DEBUG in Slave may not throw a log.
• DEBUG logging must be enabled on each node or a permanent log level change using log4j is required.

Additional Information

• Feature RequestLPS-162159
• As a workaround, you can update the log level for the entire cluster by running the following Groovy script

// Specify the new log levels

def newLogLevels = [
  "com.liferay.petra.mail": "DEBUG",
]

// Create a cluster request to update the log level on every cluster node

import com.liferay.petra.log4j.Log4JUtil
import com.liferay.petra.reflect.ReflectionUtil
import com.liferay.portal.kernel.cluster.ClusterExecutorUtil
import com.liferay.portal.kernel.cluster.ClusterRequest
import com.liferay.portal.kernel.util.MethodHandler
import java.lang.reflect.Method

Method method = ReflectionUtil.getDeclaredMethod(Log4JUtil.class, "setLevel", String.class, String.class, Boolean.TYPE)

newLogLevels.each({
  MethodHandler methodHandler = new MethodHandler(method, it.key, it.value, Boolean.TRUE)
  ClusterRequest clusterRequest = ClusterRequest.createMulticastRequest(methodHandler)
  ClusterExecutorUtil.execute(clusterRequest)
})