https://issues.apache.org/bugzilla/show_bug.cgi?id=48704
--- Comment #13 from [email protected] 2010-02-16 15:45:33 UTC --- Iam sorry .you are correct I performed my test on windows env the other day with log back ..today I compiled and ran the same code in Solaris 5.10 env with jdk150_11 and got the same results. I used TimeBasedRolling with prudent mode( as there were some constraints with using size based rolling with prudent mode in logback) and tried to roll same file from two multithreaded java instances pointing to the same log file and the rolling and logging worked well as far as I can tell found no issues with Solaris. Btw ..thank you for the fix ..I will look forward to it on the next release of log4j. (In reply to comment #12) > Reverted in rev 910151. > The independent authorship of the patch is disputed, see log4j-dev mailing > list > on 2010-02-14. Since a release push for log4j 1.2.16 is underway, it seems > prudent to pull the patch for the time being. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
