10:44:02,263 INFO [stdout] (ServerService Thread Pool -- 88) 2016-07-29 10:44:02,262 ServerService Thread Pool -- 88 ERROR No log4j2 configuration file found. Using default configuration: logging only errors to the console. 10:44:02,567 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015974: Stopped subdeployment (runtime-name: myapp-war-0-SNAPSHOT.war) in 423ms 10:44:02,572 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015877: Stopped deployment myapp.ear (runtime-name: myapp.ear) in 428ms 10:44:02,573 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of "myapp.ear" (runtime-name: "myapp.ear") 10:46:18,142 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015973: Starting subdeployment (runtime-name: "myapp-war-0-SNAPSHOT.war") 10:46:19,915 INFO [org.jboss.web] (ServerService Thread Pool -- 122) JBAS018210: Register web context: /myapp 10:46:19,939 INFO [stdout] (ServerService Thread Pool -- 122) 2016-07-29 10:46:19,938 ServerService Thread Pool -- 122 WARN WARNING: In a Servlet 3.0+ application, you should not define a log4jServletFilter in web.xml. Log4j 2 normally does this for you automatically. Log4j 2 web auto-initialization has been canceled.
On Thu, Jul 28, 2016 at 6:50 PM, Remko Popma <remko.po...@gmail.com> wrote: > That last paragraph: debug disabled, errors go to the console, sounds like > the behavior you get when Log4j2 can't find a configuration file. > > I wonder how redeploy could cause Log4j to become unable to find the > configuration... > > What do you see when you enable Log4j internal status logging? > https://logging.apache.org/log4j/2.x/faq.html#troubleshooting > > Remko > > Sent from my iPhone > > > On 2016/07/29, at 5:30, Mike Calmus <m...@calmus.org.INVALID> wrote: > > > > We are having issues with Log4j (many versions up to and including 2.6.2) > > where it works fine when an application is newly deployed and at server > > startup but where logging stops when an application is redeployed. > > > > We are using JBoss EAP 6. Applications are configured as Servlet 3.0 and > we > > are using named JNDI context selectors. > > > > Log4j is being loaded from a JBoss module rather than being bundled with > > each application. This module has core, api, web, jcl, jul and api-1.2. > > > > We are not sure if this is an EAP issue or a log4j issue, but I thought > I'd > > post to see if anyone had any ideas. > > > > Using a debugger I'm seeing that standard calls to log4j returning false > > for such things as "isDebugEnabled". Errors and such go to the JBoss > > console for these apps as though the standard configuration is being > used. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org > For additional commands, e-mail: log4j-user-h...@logging.apache.org > >
