Beware of the AWS ALB, It has a nasty bug where it terminates a chunk of
connections even if they are active. This happens after 10-12 hrs. and
related to the autoscaling of ALB.
On Thu, Jun 29, 2017 at 5:40 PM, Sandeep Dhameshia <
sandeep.dhames...@gmail.com> wrote:
> Update:
>
> Started using
(NioEndpoint.java:1437)
at
org.apache.tomcat.util.net.NioEndpoint$Poller.run(NioEndpoint.java:1231)
at java.lang.Thread.run(Thread.java:744)
On Fri, Aug 22, 2014 at 5:25 PM, anurag gupta anurag.11...@gmail.com
wrote:
Ok, So the requests will be idle upto the long poll timeout
and it is doing well and I
don't want to migrate to jetty just for long polling (implemented using
AsyncResponse).
Any suggestions ??
Regards
Anurag
On Aug 22, 2014 2:10 PM, Mark Thomas ma...@apache.org wrote:
On 22/08/2014 06:03, anurag gupta wrote:
Hi All,
I'm trying to implement long
:
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
:03 PM, Mark Thomas ma...@apache.org wrote:
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
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,
