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
>>> "scalabilitaly is equal" to a tomcat with 200 max thre
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 with
>> servlet 3's async API including applicati
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 with
> servlet 3's async API including application's thread pool with size 200.
>
> However so
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 application's thread pool with size 200.
>
> However
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 application's thread pool with size 200.
However so far I thought Oracle's docs are like standards and tomc
On 03/09/17 09:01, Yasser Zamani wrote:
> 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.
>> Sca
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
