tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "GOMEZ Henri" <>
Subject RE: mod_jk2 config
Date Mon, 04 Mar 2002 10:06:01 GMT
>With my recent changes, there are few changes in the config.
>My config is:
>( in httpd.conf )
>LoadModule jk2_module modules/
><IfModule mod_jk2.c>
>JkSet logLevel debug
>JkSet worker.ajp13.type ajp13
>JkSet socket
>JkSet worker.ajp13.port 8009


># JkSet apr
># JkSet /tmp/tomcatUnixSocket
># JkSet jni
>JkSet worker.status.type status


>JkSet /examples/* ajp13


><Location /jkstatus>
>     JkUriSet worker status

So status is a specialized worker used to display the jk state

>Both styles of uri config work ( == JkMount), uri.PROPERTY is not 
>completely implemented yet. 
>I tested only on apache2 - the apache1.3 module compiles but 
>I didn't test it. If you have some time...

I'll try to after various jakarta RPMs.

>The major change is that 'worker.NAME.type' must be the first 
>thing, and the second. 

You need this limitation to be able to verify next params ?

>In addition, worker.list is no longer used - any worker that is
>declared will be loaded.


>This is similar with server.xml - where each <BaseInterceptor>,
><Valve>, etc will be loaded if it's not commented out, and
>the object must be created before setting properties on it.
>worker.type will create a worker object ( in this case, worker is
>the interface, ajp13/status/jni is the 'class name' ). Same
>for channel, which must be instantiated.

Ok, seems fine

To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

View raw message