Re: Log to configure Log4j for multi-module EAR project

ince no one has looked at this that > none of the other committers do either. If you would care to spend some time > looking into this your help would be most welcome. > > Ralph > >> On Jan 8, 2021, at 9:42 AM, Arnold Morein >> wrote: >> >> Unusual? I do

Re: Log to configure Log4j for multi-module EAR project

our file system named “logs”? > That is a bit unusual. > > I would suggest setting status=debug on the configuration element so you can > see what the rolling file appender is resolving the file name to. > > Ralph > >> On Jan 7, 2021, at 4:17 PM, Arnold Morein >> wrote: &g

Log to configure Log4j for multi-module EAR project

I’ve looked high and low and there is nothing but vague references and comments, most of them stale. I have an EAR with two EJB modules and a WAR module. The log4j and slf4j jars are in the EAR’s /lib folder. Each module has a log4j2.xml/.dtd pair in the META-INF folder, except the WAR where

Strange error using code to set up JDBC logger

I am trying to configure a JDBC logger via code (no problems using it from XML file). I'm using Log4j2 version 2.11.2. What examples I can find are vague, incomplete, or not related. I'm finding code that may be for log4j1 and log4-jdbc but no jars in mvnrepository.com so is that old and

Log4j2 files only have 2h of data

I have an application that used to be using logback APIs and is now on log4j2. It has several log files configured like this:                     No matter how busy the given log is (some of which are very busy) only the last two hours of data are present in the current

Re: Access to current run-time config

n stop it. Another option would be to see if you can just use the JMX interface. Ralph On Feb 20, 2018, at 12:40 PM, Arnold Morein <arnie.mor...@me.com> wrote: That was it! Thanks. Next question: When I do this: LoggerContext loggerContext = (LoggerContext)LogManager.getContext(false); C

Re: Access to current run-time config

That was it! Thanks. Next question: When I do this:    LoggerContext loggerContext = (LoggerContext)LogManager.getContext(false);         Configuration loggerConfiguration = loggerContext.getConfiguration();         Map appendersType =