It seems my web.xml is ok. It's a servlet 3.1 with tomcat 8.5.32. I only have this context parameter, necessary for a correct log4j startup:
<web-app xmlns="http://xmlns.jcp.org/xml/ns/javaee"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/javaee http://xmlns.jcp.org/xml/ns/javaee/web-app_3_1.xsd"; version="3.1"> <display-name>ventusproxy</display-name> <description>ventusproxy</description> <context-param> <param-name>isLog4jContextSelectorNamed</param-name> <param-value>true</param-value> </context-param> <context-param> <param-name>log4jContextName</param-name> <param-value>ventusproxy</param-value> </context-param> ( ... ) Joan. -----Mensaje original----- De: Ralph Goers [mailto:ralph.go...@dslextreme.com] Enviado el: jueves, 27 de septiembre de 2018 18:05 Para: Log4J Users List Asunto: Re: Flush in RollingRandomAccessFile That depends on what servlet version you are using. Take a look at http://logging.apache.org/log4j/2.x/manual/webapp.html <http://logging.apache.org/log4j/2.x/manual/webapp.html>. Ralph > On Sep 27, 2018, at 9:02 AM, Joan Balagueró - ventusproxy > <joan.balagu...@ventusproxy.com> wrote: > > Hi Ralph, > > After adding the log4j-web-2.11.1.jar to our app, it doesn't work yet. > > Do I need to add something to the web.xml file, or some environment variable? > > Thanks, > > Joan. > > -----Mensaje original----- > De: Ralph Goers [mailto:ralph.go...@dslextreme.com] > Enviado el: jueves, 27 de septiembre de 2018 17:33 > Para: Log4J Users List > Asunto: Re: Flush in RollingRandomAccessFile > > Are you using the log4j-web jar? It is supposed to handle this. > > Ralph > >> On Sep 27, 2018, at 8:14 AM, Joan Balagueró - ventusproxy >> <joan.balagu...@ventusproxy.com> wrote: >> >> Hello, >> >> >> >> After sending thousands of requests to our app, we stop the sender >> and the log file appears like below: >> >> >> >> 1,54.38.179.175,2018-09-27 >> 16:55:51.618,A,13,A,39,A,72,A,120,N,,54.38.179.182:8080,g,8457,403,68 >> 3 >> ,58,ok >> ,2018-09-27 16:55:51.677 >> >> 1,54.38.179.17 >> >> >> >> Now we stop tomcat (when our app is running). And it seems the queue >> of pending events is not flushed, so the log remains like above. Our >> log configuration is: >> >> >> >> <RollingRandomAccessFile name="ACCESS_LOG" >> fileName="${sys:log.dir}vproxy_access" >> filePattern="${sys:log.dir}vproxy_access.%d{yyyy-MM-dd}" append="true" >> immediateFlush="false"> >> >> <PatternLayout> >> >> Pattern>%m%d{yyyy-MM-dd HH:mm:ss.SSS}%n</Pattern> >> >> </PatternLayout> >> >> <Policies> >> >> <CronTriggeringPolicy schedule="0 0 0 * * ?" evaluateOnStartup="true" >> /> >> >> </Policies> >> >> </RollingRandomAccessFile> >> >> >> >> <Logger name="LOGGER_ACCESS" level="info" includeLocation="false" >> additivity="false"> >> >> <AppenderRef ref="ACCESS_LOG"/> >> >> </Logger> >> >> >> >> >> >> Can we tell log4j2 to flush these pending lines when we shutdown our app? >> >> >> >> Thanks, >> >> Joan. >> >> >> > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org > For additional commands, e-mail: log4j-user-h...@logging.apache.org > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org > For additional commands, e-mail: log4j-user-h...@logging.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-user-h...@logging.apache.org
