I just setup a load balancing cluster using the IIS JK2 connector, and
spent a bit of time debugging a configuration issue. According to the
example workers2.properties, a URI should map to a load balancer with
something that looks like the following.
[uri:/examples1/*]
group=lb_1
I found
Looks like you are trying to use the module built for Apache 1.3.27 with
an Apache 2 web server. Try using the mod_jk2-2.0.43.dll binary instead.
Jonathan
On Tue, 28 Oct 2003, Jean-Max Estay wrote:
Hello,
I use the ${Apache2} in this mail for the path of my apache install
directory.
Using
On Wed, 5 Nov 2003, Andrew Davis wrote:
I've created a workers.properties file in
/usr/jakarta-tomcat-4.1.27/conf/jk. It looks like this:
# Setting variables
workers.tomcat_home=/usr/tomcat
workers.java_home=/usr/java/j2sdk1.4.1_04
ps=/
On Wed, 5 Nov 2003, Andrew Davis wrote:
Thanks. That helps. I'm playing with the options now. I notice, however,
that in the examples at:
http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jk2/jk2/configwebex.html
there are no options for specifying the path to java or tomcat anymore
as there were
There is a configuration parameter for the load balancer called
stickySession, but it should be enabled by default. You might want to
try setting it and seeing if it makes any difference. The configuration
options are described at
I've been seeing apache httpd processes consuming the processor, and I
believe it has to do with multithreading issues in JK2. I found the
following bug in the database which seems to report exactly this problem.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=27667
The thread dump of the
I've been having trouble configuring JK2 (version 2.0.2) to connect to a
Jetty server on any port other than 8009. I'm including the
workers2.properties file and the jk2.log. I've had similar results on
both IIS and Apache 1.3. Has anyone had any luck running on other ports?
The log below
Hi,
I've noticed that empty request parameters are being stripped as they
go through the JK connector.
For example, if I use the URL http://localhost/Test.jsp?a=1b=c=3, the
parameter b will be null. When not going through the connector, the
parameter b is empty string. I've tested this with
Hi,
I was having a problems with my sessions not sticking to the correct web
server in a load balanced cluster. If I set tomcatId/jvmRoute to a
value that does not contain a period, the problem goes away. I'm using
Apache 2.0.47 with JK 2.0.2.
Has anyone else seend this? Is this a known bug?
