Can anyone help regarding this ?
Update:--
A simple test on Tomcat 7.0.50/7.0.55 of Longpolling implementation using
JAX-RS 2.0 AsyncResponse mechanism.
I'm seeing the following the errors in the logs and a lot many CLOSE_WAIT
connections, Why ?
Exception in thread http-nio-8080-ClientPoller-0
On 22/08/2014 06:03, anurag gupta wrote:
Hi All,
I'm trying to implement long polling using the servlet 3.0 spec.
Implementation wise it's done and works fine in tomcat. The problem occurs
when it is under load, for eg. when we send just 100,000 requests we see
weird behaviour like
Thanks Mark.
The same application is running in a jetty9 server. And I ran a test for 5
hours with 300,000 requests (moving window of 9mins) with 10g of heap.
Jetty didn't crash with OOM. So I guess my application is not the source of
OOM.
I'm currently using tomcat 7.0.50 in production and it
On 22/08/2014 09:47, anurag gupta wrote:
Thanks Mark.
The same application is running in a jetty9 server. And I ran a test for 5
hours with 300,000 requests (moving window of 9mins) with 10g of heap.
Jetty didn't crash with OOM. So I guess my application is not the source of
OOM.
I
Executors:-
Executor name=tomcatThreadPool namePrefix=catalina-exec-
maxThreads=2048 minSpareThreads=1024 maxQueueSize=1
prestartminSpareThreads=true/
This is the connector config :-
Connector port=8080
protocol=org.apache.coyote.http11.Http11NioProtocol redirectPort=8443
On 22/08/2014 11:22, anurag gupta wrote:
Executors:-
Executor name=tomcatThreadPool namePrefix=catalina-exec-
maxThreads=2048 minSpareThreads=1024 maxQueueSize=1
prestartminSpareThreads=true/
This is the connector config :-
Connector port=8080
Ok, So the requests will be idle upto the long poll timeout if no response
is generated.
So in our test setup we have 60 clients and each makes 5000 requests.
These 5000 requests are made at the same time and renewed(i.e. a new
request is made in a loop ) as soon as
the app server sends response
Hi All,
I'm trying to implement long polling using the servlet 3.0 spec.
Implementation wise it's done and works fine in tomcat. The problem occurs
when it is under load, for eg. when we send just 100,000 requests we see
weird behaviour like requests timeout before the defined timeout,
