DO NOT REPLY [Bug 13270] - Container's AJP13 handler does not setTcpNoDelay on accept
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13270. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13270 Container's AJP13 handler does not setTcpNoDelay on accept [EMAIL PROTECTED] changed: What|Removed |Added AssignedTo|tomcat- |[EMAIL PROTECTED] |[EMAIL PROTECTED] | Status|RESOLVED|NEW - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 13270] - Container's AJP13 handler does not setTcpNoDelay on accept
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13270. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13270 Container's AJP13 handler does not setTcpNoDelay on accept --- Additional Comments From [EMAIL PROTECTED] 2002-10-04 09:05 --- There must be something wrong on your OS setup, since I never saw a ajp13 req/replie took 200ms on others boxes (Linux, Windows), may be something specific to MacOS X IP stack. BTW, the support for no delay is included : Just try to add tcpnoDelay=true in server.xml part of Ajp13. Regards -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 13270] - Container's AJP13 handler does not setTcpNoDelay on accept
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13270. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13270 Container's AJP13 handler does not setTcpNoDelay on accept --- Additional Comments From [EMAIL PROTECTED] 2002-10-04 19:44 --- Thanks Henri. Certainly, Mac OS X's IP stack can be further optimized so that the interaction between Nagle and delayed ack can be minimized (Linux, which I have tested, didn't suffer as much). But I hope it doesn't take away the fact that ajp13 protocol lends itself to be a good candidate for turning on TCP_NODELAY, by default. Anyway, I took your advice and tried to add tcpnoDelay to true. Unfortunately, it didn't work. I tried both with CoyoteConnector+JKCoyoteHandler and simply Ajp13Connector. Looking at the source codes, there is nowhere in either ChannelSocket.java nor Ajp13.java that turns TCP_NODELAY on/off. As well, the docs didn't mention that tcpnoDelay is a valid attribute in the XML element Connector. Here's part of the server.xml !-- Define a Coyote/JK2 AJP 1.3 Connector on port 8009 -- Connector className=org.apache.coyote.tomcat4.CoyoteConnector port=8009 minProcessors=5 maxProcessors=75 enableLookups=true redirectPort=8443 acceptCount=10 debug=0 connectionTimeout=2 tcpNoDelay=true useURIValidationHack=false protocolHandlerClassName=org.apache.jk.server.JkCoyoteHandler/ !-- Define an AJP 1.3 Connector on port 8009 -- !-- I tried this as well Connector className=org.apache.ajp.tomcat4.Ajp13Connector port=8009 minProcessors=5 maxProcessors=75 acceptCount=10 debug=0 tcpnoDelay=true / -- -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 13270] - Container's AJP13 handler does not setTcpNoDelay on accept
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13270. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13270 Container's AJP13 handler does not setTcpNoDelay on accept [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2002-10-04 23:33 --- For coyote - it's in jk2.properties ( where all jk properties are set ). Just set channelSocket.XXX - if you look at org.apache.jk.common.ChannelSocket you'll find all supported properties and how they are implemented. ( each property in jk2.properties is turned into a setter ). I fixed the code to actually do something with this setting :-) Not sure about the default - yet. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
