Humm... I went and looked, and I have "c:\fortius\target\fortius" as my docBase...
I believe the appliation root is just being loaded when I start up Turbine.. I think the "\/" is okay, because it does TRY to write out the log file. And if I do this: c:/fortius/target/fortius/logs/turbine.log Then it does show up.. This is with CVS head of Turbine. Eric Pugh -----Original Message----- From: Chris K Chew [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 10, 2003 11:51 AM To: Turbine Users List Subject: RE: Correct path name for logging in 2.3? > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > > For log4j, I load my properties, but I keep getting: > ConfigServlet::initLogging - log4j configuration str = > [C:\fortius\target\fortius\/WEB-INF/conf/log4j.properties] > log4j:ERROR setFile(null,false) call failed. > java.io.FileNotFoundException: \logs\turbine.log (The system > cannot find the > path specified) My log4j file looks just like yours, and it works, so I am thinking the problem is somewhere else. The "\/" looks suspicious to me. Is "C:\fortius\target\fortius\" (with the trailing \) set in server.xml, web.xml, or your path for a temporary context installation? If so, what happens if you remove the trailing "\"? Ck --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
