Doc says that the default value for the logging.type is jdk: JDK logging (default). It is correct if you are running Hazelcast in embedded mode or if you using HazelcastServerCommandLine.
But in the provided official start hz start script, the default is actually configured as log4j2.
if [ -z "$LOGGING_CONFIG" ]; then
# Use the default log4j2 file
LOGGING_CONFIG="file:$HAZELCAST_HOME/config/log4j2.properties"
else
if [ -f "$LOGGING_CONFIG" ]; then
# Try if the file exists - either absolute or relative path
LOGGING_CONFIG="file:$LOGGING_CONFIG"
elif [ -f "$HAZELCAST_HOME/config/$LOGGING_CONFIG" ]; then
# Try file in the config directory
LOGGING_CONFIG="file:$HAZELCAST_HOME/config/$LOGGING_CONFIG"
else
echo "Could not find specified LOGGING_CONFIG file."
exit 1
fi
fi
Hi, I have some feedback about this page
Doc says that the default value for the logging.type is jdk: JDK logging (default). It is correct if you are running Hazelcast in embedded mode or if you using HazelcastServerCommandLine.
But in the provided official start hz start script, the default is actually configured as log4j2.
We can update the doc to cover both scenario.