DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=24159>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=24159 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED Summary|Log4J can create deadlock |Log4J can create deadlock |conditions |conditions (concurrent | |package donation) ------- Additional Comments From [EMAIL PROTECTED] 2006-07-27 13:36 ------- Per vote on log4j-dev concluded on 2006-07-25, the concurrent package from the sandbox has been moved over to the trunk for further feedback and development. The concurrent package classes have been added to the base log4j.jar and not spun off into a log4j-concurrent.jar as previous suggested. The tests from the sandbox were not migrated from the sandbox. DeadlockTest is a test of TTCCLayout and not a test of the concurrent package and so should be in the corresponding test case. In addition, it would run out of heap space since it attempts to fire off debug requests as fast as possible for a fixed duration. PerformanceTest is not a unit test. It would be good to have unit tests that cover the new code, but I'm not undertaking that. Committed in rev 426073. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
