Hi Olivier, Making this change (immediateFlush="true") worked for me.
Activating the asyncLogger also worked as described in the docs: http://archiva.apache.org/docs/2.1.0/adminguide/logging.html -Jon On Tue, Jul 29, 2014 at 4:49 PM, Olivier Lamy <[email protected]> wrote: > You can change immediateFlush="false" to immediateFlush="true" in > log4j2.xml (in WEB-INF/classes) must fix that. > > Let us know. > > Olivier > > > > On 30 July 2014 05:04, Jonathan Sharp <[email protected]> wrote: > > Hi Bill, > > > > I also see this behavior with 2.1.0. > > > > archiva.log is continuously written when testing with 2.0.1. > > > > -Jon > > > > > > On Tue, Jul 29, 2014 at 6:13 AM, Graham,Bill <[email protected]> wrote: > > > >> All, > >> > >> I am running into an issues viewing the archiva.log file for Archiva > >> 2.1.0. I can start up the archiva server without issue, the site is > >> accessible and I get a wrapper*.log generated, but the archiva.log file > >> does not get populated with information. I did notice that when I shut > the > >> server down, the archiva.log file gets all the information written to it > >> from when the server started up, to when the server shutdown. > >> > >> Has anyone seen this behavior before? Am I missing a setting somewhere? > >> My JVM is listed below. > >> > >> Thanks, > >> > >> Bill > >> > >> > >> /usr/java/jdk1.7/bin/java -version > >> > >> java version "1.7.0_11" > >> > >> Java(TM) SE Runtime Environment (build 1.7.0_11-b21) > >> > >> Java HotSpot(TM) 64-Bit Server VM (build 23.6-b04, mixed mode) > >> > >> > > > > -- > Olivier Lamy > Ecetera: http://ecetera.com.au > http://twitter.com/olamy | http://linkedin.com/in/olamy >
