DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.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://nagoya.apache.org/bugzilla/show_bug.cgi?id=24159 Log4J can create deadlock conditions [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|WONTFIX | ------- Additional Comments From [EMAIL PROTECTED] 2003-12-18 22:27 ------- Okay, you can have your cake and eat it too. ("Have your synchronization and avoid deadlocks too"?) There are a few problems with the AppenderAttachable changes I suggest. One is that it's not efficient to maintain a vector and array. Two, iteration is effectively doubled, but this can be optimized. And I also think the cached array needs to be cleared after every add and remove, just in case an add+remove+get is done in another thread. Anyway, I'll leave that up to you to optimize and remove that boundry (somewhat) easily solved condition. I'm re-opening in the hope that you will reconsider your conclusion. I believe there are more than the two alternatives you suggest. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
