[#JETTY-315] Still getting java.nio.channels.CancelledKeyException during light load

Jetty

Still getting java.nio.channels.CancelledKeyException during light load

Created: 22/Apr/07 12:01 PM Updated: 04/May/07 02:38 AM

Component/s:

NIO

Affects Version/s:

6.1.2rc3

Fix Version/s:

None

Time Tracking:

Not Specified

Description

« Hide

We're still seeing this exception sporadically during testing:

2007-04-21T21:38:11.856 | ERROR |  0.0.0.0:8005 |                                               | log                            | EXCEPTION 
java.nio.channels.CancelledKeyException
	at sun.nio.ch.SelectionKeyImpl.ensureValid(SelectionKeyImpl.java:55)
	at sun.nio.ch.SelectionKeyImpl.interestOps(SelectionKeyImpl.java:59)
	at org.mortbay.io.nio.SelectorManager$SelectSet.doSelect(SelectorManager.java:418)
	at org.mortbay.io.nio.SelectorManager.doSelect(SelectorManager.java:175)
	at org.mortbay.jetty.nio.SelectChannelConnector.accept(SelectChannelConnector.java:124)
	at org.mortbay.jetty.AbstractConnector$Acceptor.run(AbstractConnector.java:500)
	at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:442)

All

Comments

Work Log

Change History

Sort Order:

Ascending order - Click to sort in descending order

[ Permlink | « Hide ]

Greg Wilkins - 22/Apr/07 06:31 PM

not a blocker as this is an ignorable error.... but best to suppress anyway.

As usual this is a balance between suppressing exceptions that are "normal" and not hiding
exceptions that are actually not normal.

[ Permlink | « Hide ]

Anders Wallgren - 22/Apr/07 07:04 PM

Changing the priority seems reasonable as long as you're sure there's no loss of data or signals as a result.

[ Permlink | « Hide ]

Greg Wilkins - 22/Apr/07 10:12 PM

Anders,

the SelectorManager.java:418 line does not match either rc3 or rc4 ???

The whole doSelect method is now protected with:

catch (CancelledKeyException e)

{ if (isRunning()) Log.warn(e); else Log.ignore(e); }

So I am not sure how this is happening unless you are stopping the server.

But eitherway... I am 99% sure this is an ignorable error and indicates that
the remote end has closed the connection during operations with it.
This is legal and the exception is ignorable.

[ Permlink | « Hide ]

Scott Stanton - 03/May/07 06:13 PM

This is happening for me hundreds of times a day. My logs are full of this message. Can we at least lower the reported severity of the message so I can filter it out without losing other possibly important error messages?

[ Permlink | « Hide ]

Greg Wilkins - 04/May/07 02:38 AM

reduced to just an ignore.