You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2004/07/29 15:58:18 UTC

DO NOT REPLY [Bug 30383] New: - JK2 runtime reconfiguration doesn't work on win2k3 IIS6

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=30383>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=30383

JK2 runtime reconfiguration doesn't work on win2k3 IIS6

           Summary: JK2 runtime reconfiguration doesn't work on win2k3 IIS6
           Product: Tomcat 5
           Version: 5.0.27
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: Major
          Priority: Other
         Component: Native:JK
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: bjoern@syltonline.de


I set up a proof-of-concept on a Windows 2k3 Server std-ed (patched up-to-
date) with IIS6, JK 2.0.4 and Tomcat 5.0.27. IIS acts as the frontend-
webserver and does the authentication. It passes requests to the application-
contexts to the tomcats via JK2 / AJP13.

I was glad to hear that you lot work on runtime reconfiguration for JK2, so 
that draining a tomcat-node of the cluster is possible  without loosing a 
single request or session. I got it all working nicely, having a close eye on 
the docu and status page of JK.

Problem: When i reconfigure the workers2.properties , the status page of JK 
recognizes the change nicely (scoreboard info increases version and 
says "Updated config version to 1 Status information for child 0
"). But it doesn't update to the new values! And yes, I did increase the 
version number. I can't set a worker graceful=1 or alter the LB-Factor. But 
one thing works in runtime: When I add a worker, the JK takes it without a 
problem while running. But not when I delete one. As soon as i restart the 
Application-pool, all changes are taken nicely, but that's equivalent to 
restarting the Webserver.

-----------------------------------------------------------------------
my workers.properties:
# Config-Reconfiguration ?!
[config:]
info=Defined in mod_jk2.conf.
# file=${serverRoot}/conf/workers2.properties
version=2
debug=0
debugEnv=0

[shm:]
info=Shared Memory for Scoreboard. Required for reconfiguration and status 
with multiprocess servers.
version=2
#file=D:\Java\shm\jkconector.sharedmemfile.shm
file=anonymous

# Global Parameters
[workerEnv:]
info=Global server options.
sslEnable=0
timing=0
logger=logger.file:0

# Alternate file logger (Default is System Log (Events))
[logger.file:0]
info=Where to put the mod_jk2 mainlog.
file=D:\Java\Jakarta-connector\web_tom5test-jk2.0.4\jk2.2.log
level=info

# Channel-Konfiguration
[channel.socket:localhost:8009]
info=LOCAL Worker Channel 1
version=21
port=8009
host=localhost

[channel.socket:localhost:9009]
info=LOCAL Worker Channel 2
version=21
port=9009
host=localhost

[status:status]
info=Status worker, displays runtime information

# Loadbalancer-Konfiguration
# Use even if you only have one machine.
[lb:loadbalancer]
version=18
#worker=localhost:8009
#worker=localhost:9009
timeout=10
recovery=10
attempts=3
stickySession=0

# Worker-Konfiguration
[ajp13:localhost:8009]
version=21
channel=channel.socket:localhost:8009
timeout=10
lb_factor=100
level=1
group=loadbalancer
tomcatId=TSPS1_I1
route=TSPS1_I1
graceful=0

[ajp13:localhost:9009]
version=21
channel=channel.socket:localhost:9009
timeout=10
lb_factor=100
level=1
group=loadbalancer
tomcatId=TSPS1_I2
route=TSPS1_I2
graceful=0

# URI-Mapping-Konfiguration
# Map the Tomcat examples webapp to the Web server uri space
#[uri:/jsp-examples/*]
#info=Standard-Examples, u.a. Snoop.jsp
#version=200407233
#group=lb:loadbalancer

[uri:tom5test-jk1.2.4.app.pw.de/jsp-examples/*]
#info=Standard-Examples, u.a. Snoop.jsp
#version=200407232
#debug=1
#disables=0
#context=/jsp-examples/
group=lb:loadbalancer

[uri:tom5test-jk2.0.4.app.pw.de/jsp-examples/*]
#info=Standard-Examples, u.a. Snoop.jsp
#version=200407232
#debug=1
#disables=0
#context=/jsp-examples/
group=lb:loadbalancer


[uri:/jkstatus/*]
info=The Tomcat /jkstatus handler
worker=status:status


-----------------------------------------------------------------------
My Registry-settings:
some are not nessesary, I know. ServerRoot is intended to be a random string, 
see BUG 30286.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation\Jakarta Isapi 
Redirector\2.0]
"extensionUri"="/jakarta/isapi_redirector2.dll"
"workersFile"="D:\\Java\\Jakarta-connector\\web_tom5test-jk2.0.4
\\conf\\workers2.properties"
"logLevel"="debug"
"uri_select"="parsed"
"log_file"="D:\\Java\\Jakarta-connector\\web_tom5test-jk2.0.4\\log.txt"
"serverRoot"="c:\\prrrrruuu"

Please help on this one, because Draining of nodes is vital for a clustered 
high-availability environment.

thanks
Björn Andersen

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org