[jetty-users] Apparent bug involving closing a not-so-idle connection

[Benson Margulies <bimargulies@xxxxxxxxx>]

Consider the following backtrace. I have a situation where a CXF
client makes a connection to a CXF server running jetty
7.2.0.v20101020.

In the middle of the proceedings, the channel in use in the server is
closed by this backtrace. Then both sides get a closed socket error
and sadness ensues. Is this a configuration error in how CXF sets up
jetty, a jetty bug, or something else?

SelectChannelEndPoint(ChannelEndPoint).close() line: 127	
SelectChannelEndPoint.close() line: 568	
SelectChannelEndPoint.idleExpired() line: 245	
SelectChannelEndPoint.checkIdleTimestamp(long) line: 236	
SelectorManager$SelectSet$1.run() line: 565