Hmmm, this caused me to look further into the problem... apparently our app loads a java.policy file that disallows file permissions on anything above the current directory (hey, *I* didn't write it :> )
But the more critical problem is that an exception while trying to rename the file gets thrown to the caller, which is a no-no according to the Log4J FAQ. Thanks for the help (and I subclassed RollingFileAppender to catch that exception in case it happens again! I'm surprised Log4J didn't catch it higher in the chain, however) >Is this run in an application server? __________________________________________________ Do You Yahoo!? Yahoo! Finance - Get real-time stock quotes http://finance.yahoo.com -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
