LOGGING_MANAGER=-Dnop breaks per webapp behavior or JUL about tomcat-slf4j-logback HOT 6 CLOSED

There was a bug in the latest build 7.0.54 that was distributed. Was that the drop in version you used? If so, can you try using the 8.0.9 version on sourceforge and see if you experience the same issue. The 8.0.9 version is drop in for tomcat 7 as well as it is compiled against jdk6.

from tomcat-slf4j-logback.

I didn't use a drop in zip, I compiled my own with maven and then followed the instructions in the readme. That being said, LOGGING_MANAGER=-Dnop is still set in the bundled 8 Tomcat, which makes me believe this bug still exists.

from tomcat-slf4j-logback.

Ok there was a bug in the version using tomcat 7.0.54. Can you retry your scenario with the latest build to see if that fixed it?

--- Original Message ---

From: "Miguel Pontes" [email protected]
Sent: July 9, 2014 11:33 AM
To: "grgrzybek/tomcat-slf4j-logback" [email protected]
Cc: "Jeremy Landis" [email protected]
Subject: Re: [tomcat-slf4j-logback] LOGGING_MANAGER=-Dnop breaks per webapp behavior or JUL (#37)

I didn't use a drop in zip, I compiled my own with maven and then followed the instructions in the readme.

Reply to this email directly or view it on GitHub:
#37 (comment)

from tomcat-slf4j-logback.

Retested. Compiled from the latest in master, just switched the tomcat.version in the pom.xml to 7.0.42, which is what I'm using internally. Same issue.

setenv.sh has LOGGING_MANAGER=-Dnop, Tomcat starts without any -Djava.util.logging.manager command line parameter, java.util.logging.LogManager is used as JUL's LogManager instead of org.apache.juli.ClassLoaderLogManager, which isn't multiple webapp aware. Each webapp overrides eachother's JUL configuration with LOGGING_MANAGER=-Dnop.

This has nothing to do with JCL, which I see that had some modifications in the source tree lately (nor SLF4J/Logback, for that matter). It's not related to Tomcat's internal logging either. This is an issue with pure JUL when webapps are using it.

from tomcat-slf4j-logback.

Hi Miguel
Recently I had not that much time to check this project (I have to find out why I didn't get github notifications about this issue).
I'll check this.

from tomcat-slf4j-logback.

Miguel
I've checked your scenario and deployed two webapps with separate logback.xml configurations. All applications did was to declare a listener:

    @Override
    public void contextInitialized(ServletContextEvent servletContextEvent) {
        SLF4JBridgeHandler.install();
        Logger.getLogger("grgr.test").info("Context initialized: " + servletContextEvent.getServletContext().getContextPath());
    }

    @Override
    public void contextDestroyed(ServletContextEvent servletContextEvent) {
        Logger.getLogger("grgr.test").info("Context destroyed: " + servletContextEvent.getServletContext().getContextPath());
        SLF4JBridgeHandler.uninstall();
    }

I removed LOGGING_MANAGER=-Dnop entirely (leaving Tomcat's default ClassloaderLogManager and everything worked fine. I don't remember why I had to remove it in the first place (I think this ClassloaderLogManager wasn't there initially ;)

Thanks for opening this issue - now everything works fine.

from tomcat-slf4j-logback.