Ok. I will try it myself with both of those and let you know, but it might take a couple of days.
Ralph > On Feb 19, 2019, at 11:58 PM, Paul <pgbak...@gmail.com> wrote: > > With log4j-web on the classmate the INFO statements you mentioned > disappear, but the problem of internal tomcat logging via log4j isn't > solved. > > And I've went through but those links many times, tried everything I could > find there, but no avail > >> On Tue, Feb 19, 2019, 11:26 PM Remko Popma <remko.po...@gmail.com wrote: >> >> Hi Paul, >> >> Please try adding the log4j-web jar to the classpath: >>> INFO StatusLogger Log4j appears to be running in a Servlet environment, >> but there's no log4j-web module available. If you want better web container >> support, please add the log4j-web JAR to your web archive or server lib >> directory. >> >> Also, this user manual page may be useful: >> https://logging.apache.org/log4j/2.x/manual/webapp.html (and maybe this >> one: https://logging.apache.org/log4j/2.x/manual/logsep.html). >> >> Remko. >> >> (Shameless plug) Every java main() method deserves http://picocli.info >> >>> On Feb 20, 2019, at 1:03, Paul <pgbak...@gmail.com> wrote: >>> >>> INFO StatusLogger Log4j appears to be running in a Servlet environment, >> but there's no log4j-web module available. If you want better web container >> support, please add the log4j-web JAR to your web archive or server lib >> directory. >> --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-user-h...@logging.apache.org
