https://bz.apache.org/bugzilla/show_bug.cgi?id=66482
--- Comment #5 from zhougang <zhougang6...@gmail.com> --- (In reply to Remy Maucherat from comment #4) > Ok, so that makes sense. I checked the code and both read and write can > throw this undocumented exception (there are other exceptions but they don't > occur, unlike this one apparently). > The easiest is probably going to be to do a try/catch for the whole > Nio2OperationState.run and call the completion failure with the exception. Yes, I did try/finally for the entire Nio2OperationState.run and then the problem did not occur in the test. But are there any side effects to this modification? Because we've seen elsewhere that there are isInline methods that do something based on this variable value. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
