Rainer (and all interested),
Just thought I'd let you know I threw some load at 4 Tomcats behind 1
Apache with the JK connector using domains and routes to implement two
different clusters of two Tomcats each and it seems to work well. My
load test tool (Grinder) reported that I was executing ab
Gary,
I'm not sure how much time was spent discussing alternatives as apposed
to the question of if getting access to all sessions would work.
You originally talked about tracking for concurrent license checking...
We currently do this type of thing - and more, like abstracting the
session fro
Rainer,
I thought I should just note that part of the "exotic" config (using
"route" and the like) is driven by the fact that the workers.properties
file is not dynamically reloadable.
We have had a modified version of the JK2 connector running for years
and we heavily use the capability to dyn
When I get multicast working in my Linux environment I'll put it under
load and do the same failover tests to see how it fares when it is
working harder! Maybe I'll do the same for the route/redirect method
too.
-->-Original Message-
-->From: Rainer Jung [mailto:[EMAIL PROTECTED]
-->Sent
causes problems with redirect?
-->
-->Henk Fictorie wrote:
-->>
-->> Brian.Horblit wrote:
-->>>
-->>> # Set w4 properties
-->>> worker.w4.socket_keepalive=1
-->>> worker.w4.socket_timeout=20
-->>> worker.w4.reply_timeout=2
-->>&g
Rainer,
How about a "big bug" report? Sorry for the typo ;-)
An update.
With the "route"/"redirect" strategy, I did as you suggested and changed
my "redirect" to the route name rather than the worker name. It now
seems to work as I itended: Failovers are between redirect partners. I
did a good
Rainer,
Thanks very much for the quick response! You guys are awesome.
So, as I now understand it, the "domain" mechanism is compatable with
(and independent of) the "route". And even if domains are used, the
stickyness of sticky sessions is at the server level since the route is
used to find in
All,
Good day!
For a little background, I'm working on implementing "sub-clusters" with
the new connector. That is, I will cluster my Tomcats in paris to keep
network traffic/memory usage down. The connector would preferrentially
fail-over between sub-cluster Tomcat pairs. But if both elements
Rainer,
Thanks very much for the clarification! Since I have playing with the
load balancing strategy set to session ("worker.router.method=S" on my
load balancer), is there a way to tell roughly how many sessions have
been pinned to each worker/tomcat? In this case would the load balancer
value
Ben,
So I assume you have two web servers fronting two app servers - or there
are two servers both of which have a web server and an app server? For
the restart you talk about - did you restart both web servers? Do you
have a good load balancer (local director, content director like an F5)
in fro
First, thanks in advance!
I have been playing with the 1.2.23 version of the JK Connector. In
particular, I've been setting up an Apache 2 front end to multiple
Tomcat 6's by using load balancing workers delegating to "real" workers.
For the most part the documentation is quite clear, but somethi
Kim,
You mentiond "fool-proof"... Perhaps a multi-pronged approach is best,
if you have the time and inclination to implement it.
1) Apps can have "issues" for lots of reasons (running out of memory, db
load and/or locks, thread deadlocks, etc, etc.) In lots of cases the
VM/Tomcat are "OK", but
12 matches
Mail list logo
