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=26224>. 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=26224 Concurrency policy between AsyncAppender and BoundedFIFO ------- Additional Comments From [EMAIL PROTECTED] 2004-03-04 04:20 ------- Umm, looking into this further there is a possibility of "wait"-lock here. Question: From the code, as I understand it, Many threads invoke AsyncAppender (which queues events) and one Dispacher thread (reads events)...is this correct? The problem is the use of "notify()" which could wake up (one of possibly many) waiting AsyncAppender "wait()"ing threads rather than the (desired) Dispatcher after a resize(). Some test cases I generated (with a sleep inserted in Dispatcher) can cause the "wait"-lock. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
