Re: the acceptCount attribute not work like it's configuration
On 31/12/2013 02:01, 侯树成 wrote: Hi, Today, I find the acceptCount of connector is not work like it's config. You can try it like this: Connector port=8080 protocol=HTTP/1.1 connectionTimeout=2 redirectPort=8443 acceptCount=2 maxThreads=1 minSpareThreads=1/ use LR or JMeter make more requests( 10) . You will find that 5 requests will served correctly, others will be refused. When the acceptCount=3 Connector port=8080 protocol=HTTP/1.1 connectionTimeout=2 redirectPort=8443 acceptCount=3 maxThreads=1 minSpareThreads=1/ You will find that 7 requests will served correctly, others will be refused. When the acceptCount=4 Connector port=8080 protocol=HTTP/1.1 connectionTimeout=2 redirectPort=8443 acceptCount=4 maxThreads=1 minSpareThreads=1/ You will find that 9 requests will served correctly, others will be refused. Yes, the SUCCESS requests = 2 * acceptCount + maxthead , is it right? why the acceptCount is not work like it's configuration? Could you help me? Thank you. With the information provided above, no. I have already explained how maxConnections is enforced by Tomcat. The behaviour you observe in your test will depend on the configuration of the client (number of threads, timeouts, etc.) which you have failed to provide. Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: the acceptCount attribute not work like it's configuration
Oh, everything is default in server.xml except Connector configuration. I have already explained how maxConnections is enforced by Tomcat. Where? When? I'm sorry, I havn't know it. the configuration of the client (number of threads, timeouts, etc.) -- just need a simple web app, in the servlet you can sleep 60s. Thank you for your reply. 2013/12/31 Mark Thomas ma...@apache.org On 31/12/2013 02:01, 侯树成 wrote: Hi, Today, I find the acceptCount of connector is not work like it's config. You can try it like this: Connector port=8080 protocol=HTTP/1.1 connectionTimeout=2 redirectPort=8443 acceptCount=2 maxThreads=1 minSpareThreads=1/ use LR or JMeter make more requests( 10) . You will find that 5 requests will served correctly, others will be refused. When the acceptCount=3 Connector port=8080 protocol=HTTP/1.1 connectionTimeout=2 redirectPort=8443 acceptCount=3 maxThreads=1 minSpareThreads=1/ You will find that 7 requests will served correctly, others will be refused. When the acceptCount=4 Connector port=8080 protocol=HTTP/1.1 connectionTimeout=2 redirectPort=8443 acceptCount=4 maxThreads=1 minSpareThreads=1/ You will find that 9 requests will served correctly, others will be refused. Yes, the SUCCESS requests = 2 * acceptCount + maxthead , is it right? why the acceptCount is not work like it's configuration? Could you help me? Thank you. With the information provided above, no. I have already explained how maxConnections is enforced by Tomcat. The behaviour you observe in your test will depend on the configuration of the client (number of threads, timeouts, etc.) which you have failed to provide. Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: the acceptCount attribute not work like it's configuration
On 31/12/2013 09:42, 侯树成 wrote: Oh, everything is default in server.xml except Connector configuration. Yes, I can read thanks. I have already explained how maxConnections is enforced by Tomcat. Where? When? I'm sorry, I havn't know it. You replied to my explanation so I suggest you go back and re-read the thread for your previous question. the configuration of the client (number of threads, timeouts, etc.) -- just need a simple web app, in the servlet you can sleep 60s. None of which answers my questions about the client configuration. Thank you for your reply. Mark 2013/12/31 Mark Thomas ma...@apache.org On 31/12/2013 02:01, 侯树成 wrote: Hi, Today, I find the acceptCount of connector is not work like it's config. You can try it like this: Connector port=8080 protocol=HTTP/1.1 connectionTimeout=2 redirectPort=8443 acceptCount=2 maxThreads=1 minSpareThreads=1/ use LR or JMeter make more requests( 10) . You will find that 5 requests will served correctly, others will be refused. When the acceptCount=3 Connector port=8080 protocol=HTTP/1.1 connectionTimeout=2 redirectPort=8443 acceptCount=3 maxThreads=1 minSpareThreads=1/ You will find that 7 requests will served correctly, others will be refused. When the acceptCount=4 Connector port=8080 protocol=HTTP/1.1 connectionTimeout=2 redirectPort=8443 acceptCount=4 maxThreads=1 minSpareThreads=1/ You will find that 9 requests will served correctly, others will be refused. Yes, the SUCCESS requests = 2 * acceptCount + maxthead , is it right? why the acceptCount is not work like it's configuration? Could you help me? Thank you. With the information provided above, no. I have already explained how maxConnections is enforced by Tomcat. The behaviour you observe in your test will depend on the configuration of the client (number of threads, timeouts, etc.) which you have failed to provide. Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: the acceptCount attribute not work like it's configuration
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Mark, On 12/31/13, 6:11 AM, Mark Thomas wrote: On 31/12/2013 09:42, 侯树成 wrote: Oh, everything is default in server.xml except Connector configuration. Yes, I can read thanks. I have already explained how maxConnections is enforced by Tomcat. Where? When? I'm sorry, I havn't know it. You replied to my explanation so I suggest you go back and re-read the thread for your previous question. the configuration of the client (number of threads, timeouts, etc.) -- just need a simple web app, in the servlet you can sleep 60s. None of which answers my questions about the client configuration. You might want to take a look at 侯树成's previous message under a different thread where he gives some details about server behavior which sounds odd to me: http://markmail.org/message/zvmxuagop7xiqinm - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBCAAGBQJSwtgoAAoJEBzwKT+lPKRYhhcQAKDHm3x+tQoK5D23J0jL+C5g KPI66/vIUZc+B6ilplZpVU8Zp9p4Rd8e+0uaaofC1LXq2048sbnxGah8rpoTR7EK vPeucO5XsjEE5UjxouZt+qreFI08oaQN278m6dGRp37Q+KkV7Z/oU5TJUxA1CtR6 NaCXFfDG9mpu1qQZrGFKBrXVYkljxQF0q3TZn++MLeqHmmdoIkoDxbVgZSewHAwc KPE+V23ZLYkyZ3liphOT36gDdC6YQR0P4tLxPUoKEZ1jWs3YoZP0IgJaEjd0ptmz yIxQkOnmEsxPSbRzUHJaC+6PE3iQ2U3p5KHGR2AGFAuTnPCMItU5DatMnxgOzqaz e4lYMkPwqY6hcksEY3nf9489GN2LYlrsFy0s5YtR7WsXZ9GcloIM1YnJOKoMPIvo j8gztl6lEchTx5P5z+1eMJHvo2HMhkqtQGWjsF0r/rgduY17pccV5B85JSzH0mcq er6btMNWMyMTAQqoP2u4Xbq0EoNp2LM9rmbKBAO0G8wdf9k3tQ5Mb9AsGv9ig11k izmQkLSsw2hcOJpriyceIn2H320rzsKPxZ88MYaNebNyCeaYmjjOzBO+KxFIW6w5 b6oW+O8Pf3SloGxRmLqsNbPvDLs3/X1iBF3yJu5xLSGnUTjvjZZB87UlLd6H6xbQ o2IeICyu0Bxa+Kkl7lBN =oRbc -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: the acceptCount attribute not work like it's configuration
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 31/12/2013 14:43, Christopher Schultz wrote: Mark, On 12/31/13, 6:11 AM, Mark Thomas wrote: On 31/12/2013 09:42, 侯树成 wrote: Oh, everything is default in server.xml except Connector configuration. Yes, I can read thanks. I have already explained how maxConnections is enforced by Tomcat. Where? When? I'm sorry, I havn't know it. You replied to my explanation so I suggest you go back and re-read the thread for your previous question. the configuration of the client (number of threads, timeouts, etc.) -- just need a simple web app, in the servlet you can sleep 60s. None of which answers my questions about the client configuration. You might want to take a look at 侯树成's previous message under a different thread where he gives some details about server behavior which sounds odd to me: http://markmail.org/message/zvmxuagop7xiqinm I have looked at it and, again, the expected behaviour depends on the client configuration which has yet to be provided. I do not intend wasting my time reverse engineering possible client configurations (threads, requests per thread, timeouts, etc) that could lead to the stated results. The OP needs to provide the requested information. I'll add that the longer they drag their feet that the more likely my response is going to be working as designed rather than a full explanation. Mark -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.18 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJSwtz2AAoJEBDAHFovYFnnSYkP/iWsuQ3PpjGaeV39aZIsbVJH HipTHfXU2dplPS5mag4Pp+m/HBnSK8LBAnERng54QEzJO28P7S3Ma7umZCvP0fWf 4usGDBs9fYauRXUNMUijMMY+9vaTc04e06tIUNPrR1dJnFwMnR2c8MBZn1APbD1d P4QNBultCUBoLy2B/wB4eahlqWkCc6ferdE75jBlNdux8IOnEYA6kW0NnEWg9UbD 1mkh9do4PBXcqza50RRg5xa8P8EmlBcrlnWQvqz9Q+pouWNYaZkqiQ1mzP7r1gpI qtlngswkl8O1fu2vpa7sgmNaE1RIR/7F6Lg5LmR+bFAvkV0FEvEM/kLn7TIbY+zd 3qfVj8HvnEO8LVSITTPJlSBpEJRLY7LFPu6mR95lMDoEOAFQZHVz8pbSrydtSXYH 0A5ejpPgFdlJS5Rs4Fd0ZwSZd0Xd0DZHFhCIl3e1rzEGf3L+gtm7klAZvDODRD0z 8uz+dDrMiYA9YJ0bKmO2J2NBXeWcJZ4DYuiXMrmSUpOaLjJInPc0DgIKRBM+D/4I UjuvEaYpf9GBKmiGL2qjhDxj9nXsl6JnPO6LBBDeUVXE8HD3q3ECUq7S09tTIgSx 4eVinWsjUIz0O/2JEBRVx+mOitNkbxcmMUdxTCoMVK9Bfv1xDmGPp9T651sihU0I e9fxdbbDb70SjsvI4qq+ =H0hG -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
