I managed to solve the problem, nothing to do with Tomcat actually. Turns out that I didnt configure c3p0 right so the application was being starved for db resources, causing it to look like it was hanging or crashing. Thats why there was no error in the tomcat logs, nothing went wrong with Tomcat
On Tue, Sep 16, 2014 at 12:05 PM, Elias Kopsiaftis <yemi...@gmail.com> wrote: > Hey, > > I actually answered my own question. Turns out config was not on comet > page but on connectors page for NIO connectors. > > I do have another problem though. Stress tester connects and works fine > when I lower number of connections from 20 to 10, however, when the program > exits and everything disconnects, tomcat either crashes or hangs with no > exception or error being printed in the log. Im pretty sure its tomcat and > not just the web app because tomcat manager is inaccessible as well. Any > suggestions on trouble shooting this? > > > On Tue, Sep 16, 2014 at 8:59 AM, Elias Kopsiaftis <yemi...@gmail.com> > wrote: > >> I am using Tomcat7 on Linux and was wondering, is there any way to >> increase the number of comet threads? Is there a max number of CometEvents >> that can be queued? I have a feeling either certain connections are not >> logging themselves, or they are being dropped due to an overload caused by >> my stress tester. The stress tester launches 20 threads that all connect to >> an initial servlet i use for logging in, and then to the comet servlet. The >> login servlet is logging about 19-20 connections consistently, though Im >> not sure why one is missing on occasion. >> >> >
