Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 335641

Summary:	selectKey.interestOps != endpoint.interestOps
Product:	[RT] Jetty	Reporter:	Greg Wilkins <gregw>
Component:	server	Assignee:	Greg Wilkins <gregw>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	major
Priority:	P3	CC:	jetty-inbox
Version:	7.2.0.RC0
Target Milestone:	7.2.x
Hardware:	PC
OS:	Windows All
Whiteboard:

Description Greg Wilkins

2011-01-27 19:59:36 EST

On windows platforms in some very specific circumstances (running the ConnectHandler), we have observed undispatched Endpoints where the selectKey.interestOps != endpoint.interestOps, so these endpoints are never selected and eventually timeout.

Comment 1 Greg Wilkins

2011-01-27 20:01:52 EST

This is either a bizarre windows NIO bug, or some obscure bug in Jetty SelectorManager that just happens to occur only on native Windows installations (2 at least), but not on virtual host windows or any other OS.

This strongly suggests that it has something to do with the TCP stack of windows machines - but we cannot find the smoking gun yet

Comment 2 Greg Wilkins

2011-01-27 20:28:37 EST

I've committed a work around that sweeps for the situations, logs and fixes it.
This is not a real fix, just something to get us moving forward.

Comment 3 Greg Wilkins

2011-01-30 22:19:31 EST

It turned out it was the cleanup rather than the sweep that improved the issue.  Commited removal of the sweep and general cleanup of dispatch code.  Checking now to see if problem is resolved (and why).

r2710

Comment 4 Greg Wilkins

2011-02-23 00:19:37 EST

Have not seen this with or without sweeper since other changes,