On Wed, 12 May 2004 00:05:09 +0800, Chong Yu Meng <[EMAIL PROTECTED]> wrote:
Hi,
Another way to verify if the connectors are really giving you the problems (as opposed to the application) is to setup Apache as a reverse proxy and proxy all requests to Tomcat. There is documentation on this on the
Hi,
Another way to verify if the connectors are really giving you the
problems (as opposed to the application) is to setup Apache as a reverse
proxy and proxy all requests to Tomcat. There is documentation on this
on the Tomcat site. My suspicion is that it could be your application.
Daniel
On Tue, May 11, 2004 at 11:05:34AM +0100, Adrian Barnett wrote:
: After trying numerous different things, suspicion falls on mod_jk2. The
: docs on mod_jk2 are not very helpful. Some say that mod_jk2 is better than
: mod_jk and should be used in place of it, others say that mod_jk2 is not
: stab
I *really* wish I knew the answers to your questions. Connectors are the
most frustrating part of using tomcat. But then again, I haven't tried
session replication ;-)
I don't know if the problem that I'm having is the same as yours, but I
have to kill and restart tomcat every other day or so.
Hi,
I'm having an annoying memory leak problem in tomcat5 on Redhat 9. The memory
gradually creeps up until the JVM runs out of memory. (I've been using JMeter to send
thousands of requests to tomcat)
Now, if I run the tests against tomcat by itself (via port 8080) it is fine and stable, the prob