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=42753>. 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=42753 ------- Additional Comments From [EMAIL PROTECTED] 2007-06-27 15:33 ------- (In reply to comment #3) > Since you're apparently not willing to write things that make sense, I will > ignore your report. I am getting really exasperated by your replies. You give me no hint at what it is you want or what you think is not making sense. I will test your theory more by writing a wrapper around the input stream to log the thread of every read that happens just to make sure tomorrow. In either case, after I got the error the Poller went into a busy loop. I'm not smoking pot and I saw what I saw. Ok, maybe there's a bug somewhere in my code and I'm doing something wrong, I certainly don't want to exclude that possibility. But I saw the Poller go into an infinite loop (not caused by the NIO bug I was talking about previously (which is Linux only)). It did NOT close the channel. It did NOT call my event method with a READ, ERROR or END event (which I know because I have a log.debug on enter, AND a break point set). This happened directly AFTER I got the SEVERE log message. I got this on Windows and Linux. Note that I'm not theorizing now, these are the raw observations. -- 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]
