Bug 28654 - Load balancer doesn't work for jk 2.0.4 with IIS
Summary: Load balancer doesn't work for jk 2.0.4 with IIS
Status: RESOLVED FIXED
Alias: None
Product: Tomcat Connectors
Classification: Unclassified
Component: Common (show other bugs)
Version: unspecified
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---
Assignee: Tomcat Developers Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-04-28 12:24 UTC by Dave
Modified: 2008-10-05 03:09 UTC (History)
2 users (show)



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dave 2004-04-28 12:24:37 UTC
jk2 gives the following error in the event viewer when set up with load 
balancing when the browser makes a request to that group. The browser never 
receives a response. The exact same config works fine with Apache 2.

Event Type:	Warning
Event Source:	Apache Jakarta Connector2
Event Category:	None
Event ID:	2
Date:		21/04/2004
Time:		18:50:52
User:		N/A
Computer:	DAVESXP2
Description:
Error: [jk_isapi_plugin.c (496)]: HttpExtensionProc worker is NULL
Comment 1 Martin Ramshaw 2004-05-04 04:15:45 UTC
I get exactly the sane error with Tomcat 4.1.29 on Windows 2003. 
 
I found a suggestion that the load balancing was at fault; after removing 
all references to the load balancer in the workers.prpoperties file and 
re-booting, everything worked correctly. 
 
Which brings up the question of how the workers are controlled: are they 
under the control of IIS, or are they daemon processes ? It seems that 
the only way to have them re-load their configuration details is to 
re-boot.I get exactly the sane error with Tomcat 4.1.29 on Windows 2003. 
 
I found a suggestion that the load balancing was at fault; after removing 
all references to the load balancer in the workers.prpoperties file and 
re-booting, everything worked correctly. 
 
Which brings up the question of how the workers are controlled: are they 
under the control of IIS, or are they daemon processes ? It seems that 
the only way to have them re-load their configuration details is to 
re-boot. 
Comment 2 Martin Ramshaw 2004-05-04 04:18:37 UTC
Sorry about the duplicated message. 
Comment 3 Yoav Shapira 2004-05-28 14:39:02 UTC
Please use the tomcat-user list for debugging, investigating configurations, 
inquiring about different load balancing options, etc.  This is not the place 
for a long discusssion, only exact bugs and test cases we can use to reproduce 
them.  Thanks.
Comment 4 Dave 2004-05-28 15:04:55 UTC
I wasn't starting a discussion, this is a bug. Load balancing just doesn't 
work with IIS and JK2 2.0.4. If you try it you'll see.
I use the same workers2.properties and Tomcat config for both Apache2 and IIS 
(I just switch between using Apache or IIS depending on what our customer 
wants), but I also have to comment out the group=lb and set a worker to get 
around this bug at the moment.
What sort of test case do you want? Just set up load balancing in JK2 with IIS 
and it doesn't work!!!
Comment 5 Martin Ramshaw 2004-05-28 16:56:51 UTC
I wasn't entering into a discussion about how configure load-balancing. 
 
I was giving work-around details about how to disable load-balancing 
which, as written, doesn't work. 
 
Sorry to pollute the purity of this bug log, but when something doesn't 
work for me, I check the documentation, and then the bug reports. So it 
seems to me that this is exactly the right place for this discussion. 
 
Excuse me while I write up a documentation bug ;^} 
Comment 6 Dave 2004-06-15 17:46:06 UTC
After finding a spare moment to debug the jk2 connector I've found that the 
problem was in the configuration.

I had specified 'group=lb' but should have specified 'group=lb:lb'.

This bug is now that the example workers2.properties at 
http://cvs.apache.org/viewcvs.cgi/jakarta-tomcat-
connectors/jk/conf/workers2.properties?rev=1.19&view=auto is incorrect and 
needs to be changed.

I also don't know why this hadn't gone wrong with Apache 2 (But I do think 
that changing the config fixed a cookie problem I was having under Apache 2).
Comment 7 Yoav Shapira 2004-06-16 14:46:03 UTC
OK, updated workers2.properties to have group:lb:lb and group:lb:lb_1 instead 
of group:lb and group:lb_1 (left the old versions in the file but commented 
out).