>I am reposting that patch again - let me know if there are any
>questions or
>concerns.
Costin is working on a huge refactory of jk, named native2,
and in that version the jk_init is removed from child_init.
Having it in child_init was only usefull when using ajp14
to grab URIs to be handled for a VirtualHost entry.
Since this discovery will be handled at login time, it should
be removed from child_init.
Question for Apache 2.0 experts :
Did post_config run for EACH VirtualHost or only
one time ?
In negative case, what should we use to be able to get
this init available for each VirtualHost entry ?
The key of URIs discovery in ajp14 is the virtualhost,
so we must be able to built the list of URIs handled for
each VirtualHost.
<VirtualHost xxx:80>
JkAutomout ajp14worker (xxx is implied)
</VirtualHost>
On the remote side, tomcat, there must be a VirtualHost
directive with the related webapps associated.
Some new questions here.
- How could we define webapps which could be used with all
VirtualHost on Apache side ?
ie: I want /examples webapp for all VirtualHost in Apache.
- How do we see the DEFAULT VirtualHost in Apache ? How do we
map it with Tomcat webapps ?
- What about a WebappList to be added in tomcat to be mapped later
with the requester Virtual in Apache ?
ie: in server.xml
<webapplist name="webapplist1">
<include>examples</include>
<include>ROOT</include>
</webapplist>
<webapplist name="webapplist2">
<include>admin</include>
</webapplist>
<webapplist name="webapplist3">
<include>*</include>
<exclude>admin</exclude>
</webapplist>
in httpd.conf
JkAutomout ajp14worker webapplist1
<VirtualHost xxx:443>
JkAutomout ajp14worker webapplist2
</VirtualHost>
<VirtualHost zzz:80>
JkAutomout ajp14worker webapplist3
</VirtualHost>
In such case tomcat know 3 groups of webapps,
webapplist1, webapplist2 and webapplist3.
webapplist1 explicitly cover examples and ROOT.
webapplist2 explicitly cover admin.
webapplist3 told to get all existing webapps but admin.
May ease the deployement of webapps, by using carefully
the include/exclude.
Thanks to comments.
>Seems like the latest j-t-c mod_jk calls initialization
>(init_jk) twice -
>once during post_config and then in child_init. This has a
>side effect of
>trying to create non existing workers and subsequently
>failing. Enclosed
>simple patch prevents second initialization call.
>
>Julius
>
>Index: mod_jk.c
>===================================================================
>RCS file:
>/home/cvspublic/jakarta-tomcat-connectors/jk/native/apache-2.0/
>mod_jk.c,v
>retrieving revision 1.39
>diff -u -r1.39 mod_jk.c
>--- mod_jk.c 2001/12/04 21:38:26 1.39
>+++ mod_jk.c 2001/12/05 23:56:17
>@@ -1473,7 +1473,10 @@
> jk_server_conf_t *conf =
> (jk_server_conf_t *)ap_get_module_config(s->module_config,
>&jk_module);
>
>- init_jk( pconf, conf, s );
>+ if(!conf->was_initialized) {
>+ conf->was_initialized = JK_TRUE;
>+ init_jk( pconf, conf, s );
>+ }
> }
>
> /** Initialize jk, using worker.properties.
>
>--
>To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
