We're seeing this too in 2.1.0 but did not see it in 2.0.1. Has a JIRA been created for this? It's good to know there is a simple workaround. Generally, though, 2.1.0 seems to have solved most of the problems we saw with 2.0.1. We did apply a manual patch for the cookie issue.
Jeffrey Hagelberg, Software Engineer IBM Software Group Email:[email protected] From: Jonathan Sharp <[email protected]> To: [email protected] Cc: "Bickle,Janet" <[email protected]>, "Stallard,David" <[email protected]>, "Nerderman,Adam" <[email protected]> Date: 07/29/2014 03:05 PM Subject: Re: Issues Viewing Archiva Logs 2.1.0 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) > >
