You can use the FailoverAppender as a workaround. Set up a file appender or similar as your failover option so that logging still works. Adding a feature to replay logs to an appender when it comes back online, however, would be a separate task.
On Sun, 25 Nov 2018 at 23:21, Bhavesh Patel <bhaveshhpa...@yahoo.com.invalid> wrote: > Hi Log4j2 developers, Do we have a > status on bug (https://jira.apache.org/jira/browse/LOG4J2-2162)? Or is > there a workaround for this issue? We are moving from log4j1 to log4j2 and > will be using the Kafka appender for our production systems. This would be > a major issue for us that if kafka server is down, the application itself > fails to start up and would result in loss of revenues. IS there any > recommendation to handle/bypass initializing the appender. We also have a > rolling file appender which we can fallback to. > Regards,Bhavesh. > > > -- Matt Sicker <boa...@gmail.com>
