Well to be honest I didnt know any better :-)
A friend of mine who is a better developer than I am recommended it. I have
no real reason.
On Tue, Sep 16, 2014 at 6:18 PM, Christopher Schultz <
ch...@christopherschultz.net> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Elias,
>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Elias,
On 9/16/14 4:55 PM, Elias Kopsiaftis wrote:
> 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 i
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
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 disc
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
