Re: Async logging using lmax disruptor is consuming more heap memory

org.apache.logging.log4j2:type=AsyncContext@46fbb2c1 ,component=Appenders,name=DefaultConsole-3 TRACE StatusLogger Using DummyNanoClock for nanosecond timestamps. Thanks, Ganesh S On Tue, Feb 20, 2024 at 4:43 PM Remko Popma wrote: > 197 KB for each log message! > That’s about 100-1000x large

Async logging using lmax disruptor is consuming more heap memory

logger = LogManager.getLogger(); logger.info("message1"); logger.debug("message2"); logger.error("message3"); Any input or solution is appreciated. Thanks in advance. Thanks, Ganesh S

Re: Async logger not logging after upgrading tomcat, jdk and log4j

Hello, Check the dependency hierarchy, which version of log4j is being used. I had faced similar issue, even though if I specified some particular version of log4j, maven was not picking that particular version though there were no other dependencies which were using log4j at any nested level.

Re: Adding more than one syslog appenders with different hostname and port at runtime

look into the programmatic approach that I had done, and figure out where the issue could be, since it is not pushing the message to the specified host, but the same is working in the XML approach. For the second problem, please let me know how to configure the Node object which is r

Re: Adding more than one syslog appenders with different hostname and port at runtime

Can anyone please help me on this issue? On Fri, Oct 20, 2023, 12:23 AM Ganesh S wrote: > I have made some modification in the previous code that I had sent and > there is no error or warning while configuration initialization, but logs > are not going to the destination server >

Re: Adding more than one syslog appenders with different hostname and port at runtime

ger = LogManager.getLogger("RoutingLogger"); ThreadContext.put("module", "domain#client"); logger.info("message from domain client"); logger.error("message form domain client error"); ThreadContext.remove(&

Re: Adding more than one syslog appenders with different hostname and port at runtime

ot;RoutingLogger", config.getLoggerConfig("RoutingLogger")); Configurator.reconfigure(config); LoggerContext ctx = (LoggerContext) LogManager.getContext(false); ctx.updateLoggers(); Logger logger = LogManager.getLogger("RoutingLogger");

Re: Adding more than one syslog appenders with different hostname and port at runtime

> > > On Oct 18, 2023, at 8:50 PM, Ganesh S wrote: > > > > Hello, > > I'm trying to create different logger with different hostname and port > for > > different client requests to the server. > > If a new client request comes, I will store th

Adding more than one syslog appenders with different hostname and port at runtime

onfigurationcore); org.apache.logging.log4j.core.config.Configuration newconfig = builder.build(); configurationList.add((AbstractConfiguration) newconfig); CompositeConfiguration compositeConfiguration = new CompositeConfiguration(configurationList); logContext.reconfigure(compositeConfiguration); logContext.updateLoggers(); Logger logger1 = LogManager.getLogger("client2"); logger1.info("client2 message1"); logger1.info("client2 message2"); logger.info("client1 message2"); logger1.info("client2 message3"); logger.info("client1 message3"); Thank you, Ganesh S

Need help in configuring localHostname in log4j2 syslog appender

dAttribute("appName", serviceName) .addAttribute("id", serviceName) .addAttribute("facility", "LOCAL0") .addAttribute("newLine", true) .addAttribute("format", "RFC5424") .addAttribute("ignoreExceptions", false); I'm ok to use SocketAppender as well if syslog appender doesn't support this. Thank you, Ganesh S