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=43701>. 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=43701 ------- Additional Comments From [EMAIL PROTECTED] 2007-10-30 14:22 ------- I've stumbled upon this bug too. Looks like it is being caused by the race condition between the main thread and the newly created acceptor thread. I'm getting this error quite often on my Core 2 Duo/WinXP 32-bit/Java 6u02. I think that's what happens here: 1) Acceptor thread is started at NioEndpoint:792; 2) Main thread allocates the pollers array (initially filled with nulls) at NioEndpoint:796; 3) Acceptor thread immediately catches an incoming connection and accesses the still uninitialized pollers array (inside the setSocketOptions method called at NioEndpoint:1169). Seems that poller threads should be created before starting acceptors; also, poller-related fields shall be marked volatile. -- 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]
