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 requests timeout before the defined timeout, Tomcat > goes OOM because of GC overhead limit exceeding.
The root cause of the OOM is most likely your application rather than Tomcat. > I have tried this on 2 diff versions of tomcat (mentioned in subject). > > OS CentOS 6.5 > Process memory 10g both Xmx and Xms > > So I have a question, upto how many concurrent open(idle) connections can > a tomcat instance handle ? As many as your operating system will allow. (Hint: It will be less than 100k). > How to achieve maximum idle connections ? Fix your application so it doesn't trigger an OOME. Tune your OS. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
