Re: Tomcat misuse of Servlet 3.0's asynchronous support

2017-09-19 Thread Yasser Zamani
On 9/13/2017 10:25 PM, Yasser Zamani wrote: > > > On 9/13/2017 9:49 PM, Mark Thomas wrote: >> On 05/09/2017 19:56, Yasser Zamani wrote: >>> Thanks a lot Mark! >>> >>> Yes I knew these and before tested that a tomcat with 400 max threads >>>

Re: Tomcat misuse of Servlet 3.0's asynchronous support

2017-09-13 Thread Yasser Zamani
On 9/13/2017 9:49 PM, Mark Thomas wrote: > On 05/09/2017 19:56, Yasser Zamani wrote: >> Thanks a lot Mark! >> >> Yes I knew these and before tested that a tomcat with 400 max threads >> "scalabilitaly is equal" to a tomcat with 200 max threads but wi

Re: Tomcat misuse of Servlet 3.0's asynchronous support

2017-09-13 Thread Yasser Zamani
On 9/5/2017 11:26 PM, Yasser Zamani wrote: > Thanks a lot Mark! > > Yes I knew these and before tested that a tomcat with 400 max threads > "scalabilitaly is equal" to a tomcat with 200 max threads but with > servlet 3's async API including applicati

Re: BIO: Async servlet with it's own thread pool; but get connection refused!

2017-09-12 Thread Yasser Zamani
hared between all of them to service them on demand. I'm really sorry that I bothered you a lot! Thanks a tone for your replies! Regards. On 9/12/2017 1:51 PM, Mark Thomas wrote: > On 12/09/17 10:00, Yasser Zamani wrote: >> >> >> On 9/12/2017 1:17 AM, Mark Thomas wrote

Re: BIO: Async servlet with it's own thread pool; but get connection refused!

2017-09-12 Thread Yasser Zamani
On 9/12/2017 1:17 AM, Mark Thomas wrote: > On 07/09/17 23:30, Yasser Zamani wrote: >> Thanks for your attention. >> >> Now I downloaded a fresh apache-tomcat-7.0.81-windows-x64 and chenged >> it's connector in same way (BIO,20,20,10). I get same result, fortunat

Re: BIO: Async servlet with it's own thread pool; but get connection refused!

2017-09-07 Thread Yasser Zamani
On 9/7/2017 12:15 PM, Guang Chao wrote: > On Thu, Sep 7, 2017 at 3:59 AM, Yasser Zamani > wrote: > >> Hi there, >> >> I'm studying Servlet 3's async API using tomcat. I see following strange >> behavior from tomcat in a very simple test app! >> &

Re: BIO: Async servlet with it's own thread pool; but get connection refused!

2017-09-07 Thread Yasser Zamani
JVM Version: 1.7.0_79-b15 INFO: JVM Vendor:Oracle Corporation INFO: CATALINA_BASE: C:\Users\user\.IntelliJIdea2016.3\system\tomcat\Unnamed_Async-Servlet-Example_2 Container MAX used threads: 10 Sincerely Yours, Yasser. On 9/8/2017 2:30 AM, Mark Thomas wrote: > On 07/09/1

Re: BIO: Async servlet with it's own thread pool; but get connection refused!

2017-09-07 Thread Yasser Zamani
At first thanks a lot for your reply! On 9/7/2017 1:43 PM, Mark Thomas wrote: > On 06/09/17 20:59, Yasser Zamani wrote: >> Hi there, >> >> I'm studying Servlet 3's async API using tomcat. I see following strange >> behavior from tomcat in a very simple tes

BIO: Async servlet with it's own thread pool; but get connection refused!

2017-09-06 Thread Yasser Zamani
Hi there, I'm studying Servlet 3's async API using tomcat. I see following strange behavior from tomcat in a very simple test app! I have following JMeter test plan: Number of threads (users): 700 Ramp-Up period (in seconds): 23 Loop count: 1 So JMeter generates 30.43 requests per second and 30

Re: Tomcat misuse of Servlet 3.0's asynchronous support

2017-09-05 Thread Yasser Zamani
gain except what I wrote above and also preventing deadlocks. wdyt?** On 9/5/2017 11:57 AM, Mark Thomas wrote: > On 03/09/17 09:01, Yasser Zamani wrote: >> Hi there, >> >> At [1] we read: >> >>> Web containers in application servers normally use a server t

Tomcat misuse of Servlet 3.0's asynchronous support

2017-09-03 Thread Yasser Zamani
Hi there, At [1] we read: > Web containers in application servers normally use a server thread > per client request. Under heavy load conditions, containers need a > large amount of threads to serve all the client requests. > Scalability limitations include running out of memory o