https://bz.apache.org/bugzilla/show_bug.cgi?id=58321
--- Comment #7 from Yilong Li <yilong...@runtimeverification.com> --- (In reply to Remy Maucherat from comment #3) > No idea, it sounds too specific to the NIO2 behavior. Sure the completion > handler is going to be called directly by the main thread pool, but only > once per IO operation, and since a read cannot occur until the previous one > is done it's fine as is. Sorry, I think I misunderstood your reply in my previous message. So you are saying that the completion handler cannot be called concurrently, right? Why is that? Or more precisely, what makes sure that "a read cannot occur until the previous one is done"? AsynchronousSocketChannel? CompletionHandler? Also, what do you mean by "a read is done"? After the "readCompletionHandler" in "sc.read(netInBuffer, timeout, unit, attachment, readCompletionHandler);" (https://github.com/apache/tomcat80/blob/TOMCAT_8_0_24/java/org/apache/tomcat/util/net/SecureNio2Channel.java#L792) is called? Sorry for the many questions because I am not familiar enough with the source code. -- 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
