SOLVED: Re: Tomcat 4.1.18 - IIS 5.0 plugin - jk2.properties + workers2.properties

2003-03-12 Thread Johannes Fiala
Hi to all!

I finally have found the solution:
2.0.1 and 2.0.2 is now working - it seems my try to use a different name 
for the redirector dll other than isapi_redirector2.dll has caused the 
trouble. I thought I could use isapi_redirector2_201.dll and enter it in 
the extensionUri and use it as filter in the IIS properties, but this 
didn't work.

For everybody else to save hours of desperate research, I post my complete 
configuration here:
===
registry settings (edited using regedt32.exe)
===
SOFTWARE - Apache Software Foundation - Jakarta Isapi Redirector - 2.0 
authComplete: 0
extensionUri: /jakarta/isapi_redirector2.dll
logLevel: DEBUG
serverRoot: f:\tomcat-4.1.18
threadPool: 20
workersFile: f:\tomcat-4.1.18\conf\ntiis\workers2.properties

The correct workers2.properties + jk2.properties files can be found in the 
source release (2.0.2) of the JK2 connector.
They are missing in the binary release and are not included in the 
normal Tomcat 4.1.18-distribution.
== So you have to grab them out of the source distribution. 

===
workers2.properties (location: anywhere you like, you have to point with 
the registry entry workersFile to the right filename).
===
[logger]
level=DEBUG

[config:]
file=${serverRoot}/conf/workers2.properties
debug=10
debugEnv=0

[uriMap:]
info=Maps the requests. Options: debug
debug=10

# Alternate file logger
#[logger.file:0]
#level=DEBUG
#file=${serverRoot}/logs/jk2.log

[shm:]
info=Scoreboard. Required for reconfiguration and status with multiprocess 
servers
file=${serverRoot}/logs/jk2.shm
size=100
debug=10
disabled=0

[workerEnv:]
info=Global server options
timing=1
debug=10
# Default Native Logger (apache2 or win32 )
# can be overriden to a file logger, useful
# when tracing win32 related issues
#logger=logger.file:0

[lb:lb]
info=Default load balancer.
debug=10

[lb:lb_1]
info=A second load balancer.
debug=10

[channel.socket:localhost:8009]
info=Ajp13 forwarding over socket
debug=10
tomcatId=localhost:8009

[channel.socket:localhost:8019]
info=A second tomcat instance.
debug=10
tomcatId=localhost:8019
lb_factor=1
group=lb
group=lb_1
disabled=0

[channel.un:/opt/33/work/jk2.socket]
info=A second channel connecting to localhost:8019 via unix socket
tomcatId=localhost:8019
lb_factor=1
debug=10

[channel.jni:jni]
info=The jni channel, used if tomcat is started inprocess

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

[vm:]
info=Parameters used to load a JVM in the server process
#JVM=C:\jdk\jre\bin\hotspot\jvm.dll
classpath=${TOMCAT_HOME}/bin/tomcat-jni.jar
classpath=${TOMCAT_HOME}/server/lib/commons-logging.jar
OPT=-Dtomcat.home=${TOMCAT_HOME}
OPT=-Dcatalina.home=${TOMCAT_HOME}
OPT=-Xmx128M
#OPT=-Djava.compiler=NONE
disabled=1

[worker.jni:onStartup]
info=Command to be executed by the VM on startup. This one will start 
tomcat.
class=org/apache/jk/apr/TomcatStarter
ARG=start
# For Tomcat 5 use the 'stard' for startup argument
# ARG=stard
disabled=1
stdout=${serverRoot}/logs/stdout.log
stderr=${serverRoot}/logs/stderr.log

[worker.jni:onShutdown]
info=Command to be executed by the VM on shutdown. This one will stop 
tomcat.
class=org/apache/jk/apr/TomcatStarter
ARG=stop
disabled=1

[uri:/jkstatus/*]
info=Display status information and checks the config file for changes.
group=status:

[uri:127.0.0.1:8003]
info=Example virtual host. Make sure myVirtualHost is in /etc/hosts to 
test it
alias=myVirtualHost:8003

[uri:127.0.0.1:8003/ex]
info=Example webapp in the virtual host. It'll go to lb_1 ( i.e. 
localhost:8019 )
context=/ex
group=lb_1

[uri:/examples]
info=Example webapp in the default context.
context=/examples
debug=10

[uri:/examples1/*]
info=A second webapp, this time going to the second tomcat only.
group=lb_1
debug=10

[uri:/examples/servlet/*]
info=Prefix mapping
debug=10

[uri:/examples/*.jsp]
info=Extension mapping
debug=10

[uri:/examples/*]
info=Map the whole webapp
debug=10

[uri:/examples/servlet/HelloW]
info=Example with debug enabled.
debug=10
===


===
jk2.properties (location: {$tomcat_home}/conf).
===
## THIS FILE MAY BE OVERRIDEN AT RUNTIME. MAKE SURE TOMCAT IS STOPED
## WHEN YOU EDIT THE FILE.

## COMMENTS WILL BE _LOST_

## DOCUMENTATION OF THE FORMAT IN JkMain javadoc.

# Set the desired handler list
# handler.list=apr,request,channelJni
#
# Override the default port for the socketChannel
# channelSocket.port=8019
# Default: 
# channelUnix.file=${jkHome}/work/jk2.socket
# Just to check if the the config  is working
# shm.file=${jkHome}/work/jk2.shm

# In order to enable jni use any channelJni directive
# channelJni.disabled = 0
# And one of the following directives:

# apr.jniModeSo=/opt/apache2/modules/mod_jk2.so

# If set to inprocess the mod_jk2 will Register natives itself
# This will enable the starting of the Tomcat from mod_jk2
# 

RE: SOLVED: Re: Tomcat 4.1.18 - IIS 5.0 plugin - jk2.properties + workers2.properties

2003-03-12 Thread Aparna Narla


-Original Message-
From: Johannes Fiala [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 12, 2003 2:43 PM
To: Tomcat Users List
Cc: [EMAIL PROTECTED]
Subject: SOLVED: Re: Tomcat 4.1.18 - IIS 5.0 plugin - jk2.properties +
workers2.properties


Hi to all!

I finally have found the solution:
2.0.1 and 2.0.2 is now working - it seems my try to use a different name 
for the redirector dll other than isapi_redirector2.dll has caused the 
trouble. I thought I could use isapi_redirector2_201.dll and enter it in 
the extensionUri and use it as filter in the IIS properties, but this 
didn't work.

For everybody else to save hours of desperate research, I post my complete 
configuration here:
===
registry settings (edited using regedt32.exe)
===
SOFTWARE - Apache Software Foundation - Jakarta Isapi Redirector - 2.0 
authComplete: 0
extensionUri: /jakarta/isapi_redirector2.dll
logLevel: DEBUG
serverRoot: f:\tomcat-4.1.18
threadPool: 20
workersFile: f:\tomcat-4.1.18\conf\ntiis\workers2.properties

The correct workers2.properties + jk2.properties files can be found in the 
source release (2.0.2) of the JK2 connector.
They are missing in the binary release and are not included in the 
normal Tomcat 4.1.18-distribution.
== So you have to grab them out of the source distribution. 

===
workers2.properties (location: anywhere you like, you have to point with 
the registry entry workersFile to the right filename).
===
[logger]
level=DEBUG

[config:]
file=${serverRoot}/conf/workers2.properties
debug=10
debugEnv=0

[uriMap:]
info=Maps the requests. Options: debug
debug=10

# Alternate file logger
#[logger.file:0]
#level=DEBUG
#file=${serverRoot}/logs/jk2.log

[shm:]
info=Scoreboard. Required for reconfiguration and status with multiprocess 
servers
file=${serverRoot}/logs/jk2.shm
size=100
debug=10
disabled=0

[workerEnv:]
info=Global server options
timing=1
debug=10
# Default Native Logger (apache2 or win32 )
# can be overriden to a file logger, useful
# when tracing win32 related issues
#logger=logger.file:0

[lb:lb]
info=Default load balancer.
debug=10

[lb:lb_1]
info=A second load balancer.
debug=10

[channel.socket:localhost:8009]
info=Ajp13 forwarding over socket
debug=10
tomcatId=localhost:8009

[channel.socket:localhost:8019]
info=A second tomcat instance.
debug=10
tomcatId=localhost:8019
lb_factor=1
group=lb
group=lb_1
disabled=0

[channel.un:/opt/33/work/jk2.socket]
info=A second channel connecting to localhost:8019 via unix socket
tomcatId=localhost:8019
lb_factor=1
debug=10

[channel.jni:jni]
info=The jni channel, used if tomcat is started inprocess

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

[vm:]
info=Parameters used to load a JVM in the server process
#JVM=C:\jdk\jre\bin\hotspot\jvm.dll
classpath=${TOMCAT_HOME}/bin/tomcat-jni.jar
classpath=${TOMCAT_HOME}/server/lib/commons-logging.jar
OPT=-Dtomcat.home=${TOMCAT_HOME}
OPT=-Dcatalina.home=${TOMCAT_HOME}
OPT=-Xmx128M
#OPT=-Djava.compiler=NONE
disabled=1

[worker.jni:onStartup]
info=Command to be executed by the VM on startup. This one will start 
tomcat.
class=org/apache/jk/apr/TomcatStarter
ARG=start
# For Tomcat 5 use the 'stard' for startup argument
# ARG=stard
disabled=1
stdout=${serverRoot}/logs/stdout.log
stderr=${serverRoot}/logs/stderr.log

[worker.jni:onShutdown]
info=Command to be executed by the VM on shutdown. This one will stop 
tomcat.
class=org/apache/jk/apr/TomcatStarter
ARG=stop
disabled=1

[uri:/jkstatus/*]
info=Display status information and checks the config file for changes.
group=status:

[uri:127.0.0.1:8003]
info=Example virtual host. Make sure myVirtualHost is in /etc/hosts to 
test it
alias=myVirtualHost:8003

[uri:127.0.0.1:8003/ex]
info=Example webapp in the virtual host. It'll go to lb_1 ( i.e. 
localhost:8019 )
context=/ex
group=lb_1

[uri:/examples]
info=Example webapp in the default context.
context=/examples
debug=10

[uri:/examples1/*]
info=A second webapp, this time going to the second tomcat only.
group=lb_1
debug=10

[uri:/examples/servlet/*]
info=Prefix mapping
debug=10

[uri:/examples/*.jsp]
info=Extension mapping
debug=10

[uri:/examples/*]
info=Map the whole webapp
debug=10

[uri:/examples/servlet/HelloW]
info=Example with debug enabled.
debug=10
===


===
jk2.properties (location: {$tomcat_home}/conf).
===
## THIS FILE MAY BE OVERRIDEN AT RUNTIME. MAKE SURE TOMCAT IS STOPED
## WHEN YOU EDIT THE FILE.

## COMMENTS WILL BE _LOST_

## DOCUMENTATION OF THE FORMAT IN JkMain javadoc.

# Set the desired handler list
# handler.list=apr,request,channelJni
#
# Override the default port for the socketChannel
# channelSocket.port=8019
# Default: 
# channelUnix.file=${jkHome}/work/jk2.socket
# Just to check if the the config  is working
# shm.file=${jkHome}/work/jk2.shm

# In order to enable jni use any channelJni

RE: SOLVED: Re: Tomcat 4.1.18 - IIS 5.0 plugin - jk2.properties + workers2.properties

2003-03-12 Thread Antoni Unkovich
Thanks very much, 
I was beginning to loose faith in this list as on two occasions this
week I ask for the whereabouts of the properties files to no avail.

Thanks for posting.
Antoni


 -Original Message-
 From: Aparna Narla [mailto:[EMAIL PROTECTED] 
 Sent: Thursday, 13 March 2003 10:41 a.m.
 To: 'Tomcat Users List'
 Subject: RE: SOLVED: Re: Tomcat 4.1.18 - IIS 5.0 plugin - 
 jk2.properties + workers2.properties
 
 
 
 
 -Original Message-
 From: Johannes Fiala [mailto:[EMAIL PROTECTED]
 Sent: Wednesday, March 12, 2003 2:43 PM
 To: Tomcat Users List
 Cc: [EMAIL PROTECTED]
 Subject: SOLVED: Re: Tomcat 4.1.18 - IIS 5.0 plugin - 
 jk2.properties + workers2.properties
 
 
 Hi to all!
 
 I finally have found the solution:
 2.0.1 and 2.0.2 is now working - it seems my try to use a 
 different name 
 for the redirector dll other than isapi_redirector2.dll has 
 caused the 
 trouble. I thought I could use isapi_redirector2_201.dll 
 and enter it in 
 the extensionUri and use it as filter in the IIS properties, but this 
 didn't work.
 
 For everybody else to save hours of desperate research, I 
 post my complete 
 configuration here:
 ===
 registry settings (edited using regedt32.exe) 
 === SOFTWARE - Apache Software 
 Foundation - Jakarta Isapi Redirector - 2.0 
 authComplete: 0
 extensionUri: /jakarta/isapi_redirector2.dll
 logLevel: DEBUG
 serverRoot: f:\tomcat-4.1.18
 threadPool: 20
 workersFile: f:\tomcat-4.1.18\conf\ntiis\workers2.properties
 
 The correct workers2.properties + jk2.properties files can be 
 found in the 
 source release (2.0.2) of the JK2 connector.
 They are missing in the binary release and are not included in the 
 normal Tomcat 4.1.18-distribution.
 == So you have to grab them out of the source distribution. 
 
 ===
 workers2.properties (location: anywhere you like, you have to 
 point with 
 the registry entry workersFile to the right filename). 
 === [logger] level=DEBUG
 
 [config:]
 file=${serverRoot}/conf/workers2.properties
 debug=10
 debugEnv=0
 
 [uriMap:]
 info=Maps the requests. Options: debug
 debug=10
 
 # Alternate file logger
 #[logger.file:0]
 #level=DEBUG
 #file=${serverRoot}/logs/jk2.log
 
 [shm:]
 info=Scoreboard. Required for reconfiguration and status with 
 multiprocess 
 servers
 file=${serverRoot}/logs/jk2.shm
 size=100
 debug=10
 disabled=0
 
 [workerEnv:]
 info=Global server options
 timing=1
 debug=10
 # Default Native Logger (apache2 or win32 )
 # can be overriden to a file logger, useful
 # when tracing win32 related issues
 #logger=logger.file:0
 
 [lb:lb]
 info=Default load balancer.
 debug=10
 
 [lb:lb_1]
 info=A second load balancer.
 debug=10
 
 [channel.socket:localhost:8009]
 info=Ajp13 forwarding over socket
 debug=10
 tomcatId=localhost:8009
 
 [channel.socket:localhost:8019]
 info=A second tomcat instance.
 debug=10
 tomcatId=localhost:8019
 lb_factor=1
 group=lb
 group=lb_1
 disabled=0
 
 [channel.un:/opt/33/work/jk2.socket]
 info=A second channel connecting to localhost:8019 via unix 
 socket tomcatId=localhost:8019 lb_factor=1 debug=10
 
 [channel.jni:jni]
 info=The jni channel, used if tomcat is started inprocess
 
 [status:]
 info=Status worker, displays runtime informations
 
 [vm:]
 info=Parameters used to load a JVM in the server process 
 #JVM=C:\jdk\jre\bin\hotspot\jvm.dll
 classpath=${TOMCAT_HOME}/bin/tomcat-jni.jar
 classpath=${TOMCAT_HOME}/server/lib/commons-logging.jar
 OPT=-Dtomcat.home=${TOMCAT_HOME} OPT=-Dcatalina.home=${TOMCAT_HOME}
 OPT=-Xmx128M
 #OPT=-Djava.compiler=NONE
 disabled=1
 
 [worker.jni:onStartup]
 info=Command to be executed by the VM on startup. This one will start 
 tomcat.
 class=org/apache/jk/apr/TomcatStarter
 ARG=start
 # For Tomcat 5 use the 'stard' for startup argument
 # ARG=stard
 disabled=1
 stdout=${serverRoot}/logs/stdout.log
 stderr=${serverRoot}/logs/stderr.log
 
 [worker.jni:onShutdown]
 info=Command to be executed by the VM on shutdown. This one will stop 
 tomcat.
 class=org/apache/jk/apr/TomcatStarter
 ARG=stop
 disabled=1
 
 [uri:/jkstatus/*]
 info=Display status information and checks the config file 
 for changes.
 group=status:
 
 [uri:127.0.0.1:8003]
 info=Example virtual host. Make sure myVirtualHost is in 
 /etc/hosts to 
 test it
 alias=myVirtualHost:8003
 
 [uri:127.0.0.1:8003/ex]
 info=Example webapp in the virtual host. It'll go to lb_1 ( i.e. 
 localhost:8019 )
 context=/ex
 group=lb_1
 
 [uri:/examples]
 info=Example webapp in the default context.
 context=/examples
 debug=10
 
 [uri:/examples1/*]
 info=A second webapp, this time going to the second tomcat 
 only. group=lb_1 debug=10
 
 [uri:/examples/servlet/*]
 info=Prefix mapping
 debug=10
 
 [uri:/examples/*.jsp]
 info=Extension mapping
 debug=10
 
 [uri:/examples/*]
 info=Map the whole webapp
 debug=10
 
 [uri:/examples/servlet/HelloW]
 info=Example with debug enabled.
 debug=10