Rainer Jung wrote:
Assuming that you did refresh the jkstatus display: what is your test
client? The fact that you see OK/IDLE, but all requests go to the other
node indicates, that you are using requests with associated session, so
the balancer is not allowed to send them to the other node and
s listening on
the wrong port. worker=prod_se2 failed
You should be able to trace where your config is problematic.
Kind regards / Met vriendelijke groet,
Lawrence Lamprecht
-----Original Message-
From: Matthew Laird [mailto:lai...@sfu.ca]
Sent: Tuesday, June 02, 2009 8:53 PM
To: Tomcat Use
ner.j...@kippdata.de]
Sent: Saturday, May 30, 2009 2:46 PM
To: Tomcat Users List
Subject: Re: jk Status not showing errors
On 29.05.2009 22:50, Matthew Laird wrote:
Good afternoon,
I've been trying to get the jkstatus component of mod_jk running, and
I'm not quite sure what I'm doin
Good afternoon,
I've been trying to get the jkstatus component of mod_jk running, and
I'm not quite sure what I'm doing wrong in trying to have it report dead
Tomcat instances.
I have two tomcat instances setup in a load balancer, as a test I've
taken down one of them. However the jkstatus
Caldarale, Charles R wrote:
"The only time I began to see the other cores actually start being used is when I
enabled multi-threaded GC. But that doesn't give much improvement since the threads
responding the web requests are still all on the same core."
The most likely cause is internal sy
From the OS, no.
From Tomcat, as far as I understand you can only do 2GB per Tomcat
instance. Please correct me if I'm wrong.
Jim Cox wrote:
On Thu, Oct 16, 2008 at 10:30 PM, Matthew Laird <[EMAIL PROTECTED]> wrote:
[...lines snipped...]
We have an in-house application runnin
ores actually start being used
is when I enabled multi-threaded GC. But that doesn't give much
improvement since the threads responding the web requests are still all
on the same core.
I'm not sure how to convince the Tomcat/Java container to spread its
threads among the cores.
