Log4j2 issue with hazelcast 3.8.2

160 views

Skip to first unread message

Joan Balagueró

unread,

Jun 8, 2017, 5:50:26 AM6/8/17

to Hazelcast

Hello,

Using the RollingFileAppender (latest version of log4j2) and telling hazelcast to use this log, I get this error:

2017-05-26 00:00:00,846 hz._hzInstance_1_ventusproxy01.ventusproxy.com.HealthMonitor ERROR An exception occurred processing Appender SYSTEM_LOG java.lang.NullPointerException: activeFileName

at java.util.Objects.requireNonNull(Objects.java:228)

at org.apache.logging.log4j.core.appender.rolling.RolloverDescriptionImpl.<init>(RolloverDescriptionImpl.java:60)

at org.apache.logging.log4j.core.appender.rolling.DirectWriteRolloverStrategy.rollover(DirectWriteRolloverStrategy.java:194)

at org.apache.logging.log4j.core.appender.rolling.RollingFileManager.rollover(RollingFileManager.java:362)

at org.apache.logging.log4j.core.appender.rolling.RollingFileManager.rollover(RollingFileManager.java:278)

at org.apache.logging.log4j.core.appender.rolling.RollingFileManager.checkRollover(RollingFileManager.java:218)

at org.apache.logging.log4j.core.appender.RollingFileAppender.append(RollingFileAppender.java:267)

at org.apache.logging.log4j.core.config.AppenderControl.tryCallAppender(AppenderControl.java:156)

at org.apache.logging.log4j.core.config.AppenderControl.callAppender0(AppenderControl.java:129)

at org.apache.logging.log4j.core.config.AppenderControl.callAppenderPreventRecursion(AppenderControl.java:120)

at org.apache.logging.log4j.core.config.AppenderControl.callAppender(AppenderControl.java:84)

at org.apache.logging.log4j.core.config.LoggerConfig.callAppenders(LoggerConfig.java:448)

at org.apache.logging.log4j.core.config.LoggerConfig.processLogEvent(LoggerConfig.java:433)

at org.apache.logging.log4j.core.config.LoggerConfig.log(LoggerConfig.java:417)

at org.apache.logging.log4j.core.config.LoggerConfig.log(LoggerConfig.java:403)

at org.apache.logging.log4j.core.config.AwaitCompletionReliabilityStrategy.log(AwaitCompletionReliabilityStrategy.java:63)

at org.apache.logging.log4j.core.Logger.logMessage(Logger.java:146)

at org.apache.logging.log4j.spi.AbstractLogger.logMessageSafely(AbstractLogger.java:2091)

at org.apache.logging.log4j.spi.AbstractLogger.logMessage(AbstractLogger.java:1988)

at org.apache.logging.log4j.spi.AbstractLogger.logIfEnabled(AbstractLogger.java:1960)

at com.hazelcast.logging.Log4j2Factory$Log4j2Logger.log(Log4j2Factory.java:59)

at com.hazelcast.logging.LoggingServiceImpl$DefaultLogger.log(LoggingServiceImpl.java:168)

at com.hazelcast.logging.LoggingServiceImpl$DefaultLogger.log(LoggingServiceImpl.java:158)

at com.hazelcast.internal.diagnostics.HealthMonitor$HealthMonitorThread.run(HealthMonitor.java:152)

I'd say this is because the "fileName" is no longer mandatory. I'm not using it in the log4j.xml, just the file pattern:

<RollingFile name="ACCESS_LOG"

filePattern="${sys:log.dir}vproxy_access.%d{${sys:log.rotateAccess}}"

append="true"

bufferedIO="true"

bufferSize="16384"

immediateFlush="false">

</PatternLayout>

</Policies>

</RollingFile>

Regards,

Joan.

Mehmet Dogan

unread,

Jun 8, 2017, 5:58:25 AM6/8/17

to Hazelcast

I think you should ask this to Log4j folks.

--
You received this message because you are subscribed to the Google Groups "Hazelcast" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hazelcast+...@googlegroups.com.
To post to this group, send email to haze...@googlegroups.com.
Visit this group at https://groups.google.com/group/hazelcast.
To view this discussion on the web visit https://groups.google.com/d/msgid/hazelcast/85ffb1e9-5ddd-4fbd-9665-af11762fdbde%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.