Sample http.conf and worker.properties file
Hi, Could anyone send me the sample http.conf and worker.porperties file for mod_jk with Apache 2 and Tomcat 5 on windows 2000 ? Any help will be highly appreciated. Regards, Rehman Adil - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Sample http.conf and worker.properties file ?????
Hi, Could anyone send me the sample http.conf and worker.porperties file for mod_jk with Apache 2 and Tomcat 5 on windows 2000 ? Any help will be highly appreciated. Regards, Rehman Adil - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cachesize in worker.properties for mod_jk on tomcat404
I've set this to two. I would have thought that this would make me only have to do two HTTP requests to apache, after a tomcat restart, before getting a proper connection. Is this the case, or no? How does this property actually work? I get an internal server error on apache multiple times before getting a good connection to tomcat. __ This communication is intended for the use of the recipient to whom it is addressed, and may contain confidential, personal, and or privileged information. Please contact us immediately if you are not the intended recipient of this communication, and do not copy, distribute, or take action relying on it. Any communications received in error, or subsequent reply, should be deleted or destroyed. --- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: worker.properties
Hi - Please clarify: do you have multiple Tomcat instances, or just one? The only time you need to put more hosts in workers.properties is if you have MULTIPLE Tomcat instances. If you only have one Tomcat instance, you only need the following in workers.properties: # BEGIN workers.properties # Definition for Ajp13 worker worker.list=ajp13 worker.ajp13.port=8009 worker.ajp13.host=localhost worker.ajp13.type=ajp13 # END workers.properties Note that it is workers.properties, not worker.properties (note the missing s in your post...a typo?). Note also that for IIS, you need more than workers.properties...you also need a file called uriworkermap.properties. Workers.properties is not for the purpose of mapping virtual hosts...its only purpose is to tell the connector where to find Tomcat. If you have one Tomcat instance, and a workers.properties file like the one shown above, and you cannot get any host headers except localhost to work, your problem is in either or both of 1) defining/mapping virtual hosts on the web server side (IIS: uriworkermap.properties, Apache: JkMount), or 2) defining virtual hosts on the Tomcat side. Even if you have multiple Tomcat instances, I would suggest getting things to work for multiple virtual hosts using one Tomcat instance, then add the other Tomcat instances into the mix. Trying to get multiple Tomcat instances working with multiple virtual hosts all at once could easily become frustrating if you don't take it a step or piece at a time. John On Thu, 19 Jun 2003 17:03:30 -0500, Jose Santiago Oyervides Gonzalez [EMAIL PROTECTED] wrote: Hi, Could anyone tell me what would be the correct configuration in the worker.properties to allow IIS to redirect to multiple hosts. Currently I am using this: (with no success,only for localhost) worker.properties: worker.ajp13.type=ajp13 worker.work.type=ajp13 worker.tomcat_home=D:\Tomcat4 worker.java_home=C:\j2sdk1.4.0 ps=\ worker.list=ajp13,myworker,myworker2 worker.ajp13.port=8009 worker.ajp13.host=localhost worker.myworker.port=8009 worker.myworker.host=foo.com worker.myworker2.port=8009 worker.myworker2.host=otherhost.com I am using Tomcat 4.0.6 -- IIS 5.0. According the 4.1.X documentation my configuration is valid, but I wonder if that works in 4.0.X. ¿? Also in server.xml, I specified the address property for the ip of the domains I'm configuring.(and added the hosts,obviously) Regards. Jose Oyervides. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: worker.properties
Thanks John, You were right, I only needed to add localhost in my worker.properties, now it's working. I'm using Tomcat 4.0.6 with one instance and using worker.properties, uriworkermap.properties and isapi_redirector.dll, just configured the localhost in my worker.properties and everything is now working. I read the FAQ for tomcat 4.1.X and got confused, since I didn't find the worker.properties configuration for tomcat 4.0.X, I followed the 4.1.X one. Thanks a lot John! Regards. Jose Oyervides. -Original Message- From: John Turner [mailto:[EMAIL PROTECTED] Sent: Friday, June 20, 2003 7:50 AM To: Tomcat Users List Subject: Re: worker.properties Hi - Please clarify: do you have multiple Tomcat instances, or just one? The only time you need to put more hosts in workers.properties is if you have MULTIPLE Tomcat instances. If you only have one Tomcat instance, you only need the following in workers.properties: # BEGIN workers.properties # Definition for Ajp13 worker worker.list=ajp13 worker.ajp13.port=8009 worker.ajp13.host=localhost worker.ajp13.type=ajp13 # END workers.properties Note that it is workers.properties, not worker.properties (note the missing s in your post...a typo?). Note also that for IIS, you need more than workers.properties...you also need a file called uriworkermap.properties. Workers.properties is not for the purpose of mapping virtual hosts...its only purpose is to tell the connector where to find Tomcat. If you have one Tomcat instance, and a workers.properties file like the one shown above, and you cannot get any host headers except localhost to work, your problem is in either or both of 1) defining/mapping virtual hosts on the web server side (IIS: uriworkermap.properties, Apache: JkMount), or 2) defining virtual hosts on the Tomcat side. Even if you have multiple Tomcat instances, I would suggest getting things to work for multiple virtual hosts using one Tomcat instance, then add the other Tomcat instances into the mix. Trying to get multiple Tomcat instances working with multiple virtual hosts all at once could easily become frustrating if you don't take it a step or piece at a time. John On Thu, 19 Jun 2003 17:03:30 -0500, Jose Santiago Oyervides Gonzalez [EMAIL PROTECTED] wrote: Hi, Could anyone tell me what would be the correct configuration in the worker.properties to allow IIS to redirect to multiple hosts. Currently I am using this: (with no success,only for localhost) worker.properties: worker.ajp13.type=ajp13 worker.work.type=ajp13 worker.tomcat_home=D:\Tomcat4 worker.java_home=C:\j2sdk1.4.0 ps=\ worker.list=ajp13,myworker,myworker2 worker.ajp13.port=8009 worker.ajp13.host=localhost worker.myworker.port=8009 worker.myworker.host=foo.com worker.myworker2.port=8009 worker.myworker2.host=otherhost.com I am using Tomcat 4.0.6 -- IIS 5.0. According the 4.1.X documentation my configuration is valid, but I wonder if that works in 4.0.X. ¿? Also in server.xml, I specified the address property for the ip of the domains I'm configuring.(and added the hosts,obviously) Regards. Jose Oyervides. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: worker.properties
No problem, glad I could help. John On Fri, 20 Jun 2003 11:29:37 -0500, Jose Santiago Oyervides Gonzalez [EMAIL PROTECTED] wrote: Thanks John, You were right, I only needed to add localhost in my worker.properties, now it's working. I'm using Tomcat 4.0.6 with one instance and using worker.properties, uriworkermap.properties and isapi_redirector.dll, just configured the localhost in my worker.properties and everything is now working. I read the FAQ for tomcat 4.1.X and got confused, since I didn't find the worker.properties configuration for tomcat 4.0.X, I followed the 4.1.X one. Thanks a lot John! Regards. Jose Oyervides. -Original Message- From: John Turner [mailto:[EMAIL PROTECTED] Sent: Friday, June 20, 2003 7:50 AM To: Tomcat Users List Subject: Re: worker.properties Hi - Please clarify: do you have multiple Tomcat instances, or just one? The only time you need to put more hosts in workers.properties is if you have MULTIPLE Tomcat instances. If you only have one Tomcat instance, you only need the following in workers.properties: # BEGIN workers.properties # Definition for Ajp13 worker worker.list=ajp13 worker.ajp13.port=8009 worker.ajp13.host=localhost worker.ajp13.type=ajp13 # END workers.properties Note that it is workers.properties, not worker.properties (note the missing s in your post...a typo?). Note also that for IIS, you need more than workers.properties...you also need a file called uriworkermap.properties. Workers.properties is not for the purpose of mapping virtual hosts...its only purpose is to tell the connector where to find Tomcat. If you have one Tomcat instance, and a workers.properties file like the one shown above, and you cannot get any host headers except localhost to work, your problem is in either or both of 1) defining/mapping virtual hosts on the web server side (IIS: uriworkermap.properties, Apache: JkMount), or 2) defining virtual hosts on the Tomcat side. Even if you have multiple Tomcat instances, I would suggest getting things to work for multiple virtual hosts using one Tomcat instance, then add the other Tomcat instances into the mix. Trying to get multiple Tomcat instances working with multiple virtual hosts all at once could easily become frustrating if you don't take it a step or piece at a time. John On Thu, 19 Jun 2003 17:03:30 -0500, Jose Santiago Oyervides Gonzalez [EMAIL PROTECTED] wrote: Hi, Could anyone tell me what would be the correct configuration in the worker.properties to allow IIS to redirect to multiple hosts. Currently I am using this: (with no success,only for localhost) worker.properties: worker.ajp13.type=ajp13 worker.work.type=ajp13 worker.tomcat_home=D:\Tomcat4 worker.java_home=C:\j2sdk1.4.0 ps=\ worker.list=ajp13,myworker,myworker2 worker.ajp13.port=8009 worker.ajp13.host=localhost worker.myworker.port=8009 worker.myworker.host=foo.com worker.myworker2.port=8009 worker.myworker2.host=otherhost.com I am using Tomcat 4.0.6 -- IIS 5.0. According the 4.1.X documentation my configuration is valid, but I wonder if that works in 4.0.X. ¿? Also in server.xml, I specified the address property for the ip of the domains I'm configuring.(and added the hosts,obviously) Regards. Jose Oyervides. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
worker.properties
Hi, Could anyone tell me what would be the correct configuration in the worker.properties to allow IIS to redirect to multiple hosts. Currently I am using this: (with no success,only for localhost) worker.properties: worker.ajp13.type=ajp13 worker.work.type=ajp13 worker.tomcat_home=D:\Tomcat4 worker.java_home=C:\j2sdk1.4.0 ps=\ worker.list=ajp13,myworker,myworker2 worker.ajp13.port=8009 worker.ajp13.host=localhost worker.myworker.port=8009 worker.myworker.host=foo.com worker.myworker2.port=8009 worker.myworker2.host=otherhost.com I am using Tomcat 4.0.6 -- IIS 5.0. According the 4.1.X documentation my configuration is valid, but I wonder if that works in 4.0.X. ¿? Also in server.xml, I specified the address property for the ip of the domains I'm configuring.(and added the hosts,obviously) Regards. Jose Oyervides. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
solved AW: worker.properties swallows my first worker (mod_jk)
As Costin pointed out, the error was a cut and paste one. my worker.list started with worker.list=worker.list= ajp12 It should of course be worker.list=ajp12 This typo caused interseting effects though ;) Thanks very much for your help. Regards, Hans -Ursprüngliche Nachricht- Von: Larry Isaacs [mailto:[EMAIL PROTECTED]] Gesendet: Donnerstag, 6. September 2001 19:39 An: '[EMAIL PROTECTED]' Betreff: RE: worker.properties swallows my first worker (mod_jk) Hi Hans, The answers to your questions are: 1.) Why gets this hardcoded worker on port 8007 created? Don't know, I will investigate. 2.) Is this a Bug I shall report? Yes, and please attache the workers.properties in question. Thanks. Larry -Original Message- From: Hans Schmid [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 06, 2001 12:57 PM To: Tomcat-User Subject: worker.properties swallows my first worker (mod_jk) Hello, This is about mod_jk in Tomcat 3.3b1 on Solaris with Apache 1.3.19 It seems to me that the first worker found in the worker.list always gets created as ajp12 on port 8007 regardless what i configure. The following worker.list entry worker.list=worker.list=ajp12-01, ajp12-02, ajp13-01, ajp13-02 produces 4 workers: ajp12-01 on port 8007 ajp12 ajp12-02 on port 9017 ajp12 ajp13-01 on port 9009 ajp13 ajp13-02 on port 9019 ajp13 instead of the expected: ajp12-01 on port 9007 ajp12 ajp12-02 on port 9017 ajp12 ajp13-01 on port 9009 ajp13 ajp13-02 on port 9019 ajp13 Please note the ajp12-01 worker points to port 8007 instead of 9007. When I put a space in front of the first worker I get my expected 4 workers pointing to the correct ports plus a 5th worker ('' on port 8007) The following entry in workers.properties worker.list=worker.list= ajp12-01, ajp12-02, ajp13-01, ajp13-02 produces 5 workers instead of 4 Please note the port 8007 for the first worker named worker.list= of ajp12 I do not have a worker assigned to this port (greped through all config files). [Thu Sep 06 18:26:17 2001] [jk_worker.c (207)]: Into build_worker_map, creating 5 workers [Thu Sep 06 18:26:17 2001] [jk_worker.c (213)]: build_worker_map, creating worker worker.list= [Thu Sep 06 18:26:17 2001] [jk_worker.c (138)]: Into wc_create_worker [Thu Sep 06 18:26:17 2001] [jk_worker.c (152)]: wc_create_worker, about to create instance worker.list= of ajp12 [Thu Sep 06 18:26:17 2001] [jk_ajp12_worker.c (264)]: Into ajp12_worker_factory [Thu Sep 06 18:26:17 2001] [jk_worker.c (161)]: wc_create_worker, about to validate and init worker.list= [Thu Sep 06 18:26:17 2001] [jk_ajp12_worker.c (182)]: Into jk_worker_t::validate [Thu Sep 06 18:26:17 2001] [jk_ajp12_worker.c (194)]: In jk_worker_t::validate for worker worker.list= contact is localhost:8007 [Thu Sep 06 18:26:17 2001] [jk_worker.c (177)]: wc_create_worker, done [Thu Sep 06 18:26:17 2001] [jk_worker.c (223)]: build_worker_map, removing old worker.list= worker [Thu Sep 06 18:26:17 2001] [jk_worker.c (213)]: build_worker_map, creating worker ajp12-01 [Thu Sep 06 18:26:17 2001] [jk_worker.c (138)]: Into wc_create_worker [Thu Sep 06 18:26:17 2001] [jk_worker.c (152)]: wc_create_worker, about to create instance ajp12-01 of ajp12 [Thu Sep 06 18:26:17 2001] [jk_ajp12_worker.c (264)]: Into ajp12_worker_factory [Thu Sep 06 18:26:17 2001] [jk_worker.c (161)]: wc_create_worker, about to validate and init ajp12-01 [Thu Sep 06 18:26:17 2001] [jk_ajp12_worker.c (182)]: Into jk_worker_t::validate [Thu Sep 06 18:26:17 2001] [jk_ajp12_worker.c (194)]: In jk_worker_t::validate for worker ajp12-01 contact is localhost:9007 [Thu Sep 06 18:26:17 2001] [jk_worker.c (177)]: wc_create_worker, done [Thu Sep 06 18:26:17 2001] [jk_worker.c (223)]: build_worker_map, removing old ajp12-01 worker [Thu Sep 06 18:26:17 2001] [jk_worker.c (213)]: build_worker_map, creating worker ajp12-02 [Thu Sep 06 18:26:17 2001] [jk_worker.c (138)]: Into wc_create_worker [Thu Sep 06 18:26:17 2001] [jk_worker.c (152)]: wc_create_worker, about to create instance ajp12-02 of ajp12 [Thu Sep 06 18:26:17 2001] [jk_ajp12_worker.c (264)]: Into ajp12_worker_factory [Thu Sep 06 18:26:17 2001] [jk_worker.c (161)]: wc_create_worker, about to validate and init ajp12-02 [Thu Sep 06 18:26:17 2001] [jk_ajp12_worker.c (182)]: Into jk_worker_t::validate [Thu Sep 06 18:26:17 2001] [jk_ajp12_worker.c (194)]: In jk_worker_t::validate for worker ajp12-02 contact is localhost:9017 [Thu Sep 06 18:26:17 2001] [jk_worker.c (177)]: wc_create_worker, done [Thu Sep 06 18:26:17 2001] [jk_worker.c (223)]: build_worker_map, removing old ajp12-02 worker [Thu Sep 06 18:26:17 2001] [jk_worker.c (213)]: build_worker_map, creating worker ajp13-01 [Thu Sep 06 18:26:17
Re: worker.properties swallows my first worker (mod_jk)
Hans Schmid wrote: Hello, This is about mod_jk in Tomcat 3.3b1 on Solaris with Apache 1.3.19 It seems to me that the first worker found in the worker.list always gets created as ajp12 on port 8007 regardless what i configure. The following worker.list entry worker.list=worker.list=ajp12-01, ajp12-02, ajp13-01, ajp13-02 --! TYPO!!! produces 4 workers: ajp12-01 on port 8007 ajp12 ajp12-02 on port 9017 ajp12 ajp13-01 on port 9009 ajp13 ajp13-02 on port 9019 ajp13 instead of the expected: ajp12-01 on port 9007 ajp12 ajp12-02 on port 9017 ajp12 ajp13-01 on port 9009 ajp13 ajp13-02 on port 9019 ajp13 Please note the ajp12-01 worker points to port 8007 instead of 9007. When I put a space in front of the first worker I get my expected 4 workers pointing to the correct ports plus a 5th worker ('' on port 8007) The following entry in workers.properties worker.list=worker.list= ajp12-01, ajp12-02, ajp13-01, ajp13-02 produces 5 workers instead of 4 Please note the port 8007 for the first worker named worker.list= of ajp12 I do not have a worker assigned to this port (greped through all config files). [Thu Sep 06 18:26:17 2001] [jk_worker.c (207)]: Into build_worker_map, creating 5 workers [Thu Sep 06 18:26:17 2001] [jk_worker.c (213)]: build_worker_map, creating worker worker.list= [Thu Sep 06 18:26:17 2001] [jk_worker.c (138)]: Into wc_create_worker [Thu Sep 06 18:26:17 2001] [jk_worker.c (152)]: wc_create_worker, about to create instance worker.list= of ajp12 [Thu Sep 06 18:26:17 2001] [jk_ajp12_worker.c (264)]: Into ajp12_worker_factory [Thu Sep 06 18:26:17 2001] [jk_worker.c (161)]: wc_create_worker, about to validate and init worker.list= [Thu Sep 06 18:26:17 2001] [jk_ajp12_worker.c (182)]: Into jk_worker_t::validate [Thu Sep 06 18:26:17 2001] [jk_ajp12_worker.c (194)]: In jk_worker_t::validate for worker worker.list= contact is localhost:8007 [Thu Sep 06 18:26:17 2001] [jk_worker.c (177)]: wc_create_worker, done [Thu Sep 06 18:26:17 2001] [jk_worker.c (223)]: build_worker_map, removing old worker.list= worker [Thu Sep 06 18:26:17 2001] [jk_worker.c (213)]: build_worker_map, creating worker ajp12-01 [Thu Sep 06 18:26:17 2001] [jk_worker.c (138)]: Into wc_create_worker [Thu Sep 06 18:26:17 2001] [jk_worker.c (152)]: wc_create_worker, about to create instance ajp12-01 of ajp12 [Thu Sep 06 18:26:17 2001] [jk_ajp12_worker.c (264)]: Into ajp12_worker_factory [Thu Sep 06 18:26:17 2001] [jk_worker.c (161)]: wc_create_worker, about to validate and init ajp12-01 [Thu Sep 06 18:26:17 2001] [jk_ajp12_worker.c (182)]: Into jk_worker_t::validate [Thu Sep 06 18:26:17 2001] [jk_ajp12_worker.c (194)]: In jk_worker_t::validate for worker ajp12-01 contact is localhost:9007 [Thu Sep 06 18:26:17 2001] [jk_worker.c (177)]: wc_create_worker, done [Thu Sep 06 18:26:17 2001] [jk_worker.c (223)]: build_worker_map, removing old ajp12-01 worker [Thu Sep 06 18:26:17 2001] [jk_worker.c (213)]: build_worker_map, creating worker ajp12-02 [Thu Sep 06 18:26:17 2001] [jk_worker.c (138)]: Into wc_create_worker [Thu Sep 06 18:26:17 2001] [jk_worker.c (152)]: wc_create_worker, about to create instance ajp12-02 of ajp12 [Thu Sep 06 18:26:17 2001] [jk_ajp12_worker.c (264)]: Into ajp12_worker_factory [Thu Sep 06 18:26:17 2001] [jk_worker.c (161)]: wc_create_worker, about to validate and init ajp12-02 [Thu Sep 06 18:26:17 2001] [jk_ajp12_worker.c (182)]: Into jk_worker_t::validate [Thu Sep 06 18:26:17 2001] [jk_ajp12_worker.c (194)]: In jk_worker_t::validate for worker ajp12-02 contact is localhost:9017 [Thu Sep 06 18:26:17 2001] [jk_worker.c (177)]: wc_create_worker, done [Thu Sep 06 18:26:17 2001] [jk_worker.c (223)]: build_worker_map, removing old ajp12-02 worker [Thu Sep 06 18:26:17 2001] [jk_worker.c (213)]: build_worker_map, creating worker ajp13-01 [Thu Sep 06 18:26:17 2001] [jk_worker.c (138)]: Into wc_create_worker [Thu Sep 06 18:26:17 2001] [jk_worker.c (152)]: wc_create_worker, about to create instance ajp13-01 of ajp13 [Thu Sep 06 18:26:17 2001] [jk_ajp13_worker.c (882)]: Into ajp13_worker_factory [Thu Sep 06 18:26:17 2001] [jk_worker.c (161)]: wc_create_worker, about to validate and init ajp13-01 [Thu Sep 06 18:26:17 2001] [jk_ajp13_worker.c (412)]: Into jk_worker_t::validate [Thu Sep 06 18:26:17 2001] [jk_ajp13_worker.c (425)]: In jk_worker_t::validate for worker ajp13-01 contact is localhost:9009 [Thu Sep 06 18:26:17 2001] [jk_ajp13_worker.c (451)]: Into jk_worker_t::init [Thu Sep 06 18:26:17 2001] [jk_worker.c (177)]: wc_create_worker, done [Thu Sep 06 18:26:17 2001] [jk_worker.c (223)]: build_worker_map, removing old ajp13-01 worker [Thu Sep 06 18:26:17 2001] [jk_worker.c (213)]: build_worker_map, creating worker ajp13-02 and one ajp13-02 on port 9019 My questions: 1.) Why gets this hardcoded worker on port 8007 created? 2.) Is this a Bug I shall
worker.properties swallows my first worker (mod_jk)
Hello, This is about mod_jk in Tomcat 3.3b1 on Solaris with Apache 1.3.19 It seems to me that the first worker found in the worker.list always gets created as ajp12 on port 8007 regardless what i configure. The following worker.list entry worker.list=worker.list=ajp12-01, ajp12-02, ajp13-01, ajp13-02 produces 4 workers: ajp12-01 on port 8007 ajp12 ajp12-02 on port 9017 ajp12 ajp13-01 on port 9009 ajp13 ajp13-02 on port 9019 ajp13 instead of the expected: ajp12-01 on port 9007 ajp12 ajp12-02 on port 9017 ajp12 ajp13-01 on port 9009 ajp13 ajp13-02 on port 9019 ajp13 Please note the ajp12-01 worker points to port 8007 instead of 9007. When I put a space in front of the first worker I get my expected 4 workers pointing to the correct ports plus a 5th worker ('' on port 8007) The following entry in workers.properties worker.list=worker.list= ajp12-01, ajp12-02, ajp13-01, ajp13-02 produces 5 workers instead of 4 Please note the port 8007 for the first worker named worker.list= of ajp12 I do not have a worker assigned to this port (greped through all config files). [Thu Sep 06 18:26:17 2001] [jk_worker.c (207)]: Into build_worker_map, creating 5 workers [Thu Sep 06 18:26:17 2001] [jk_worker.c (213)]: build_worker_map, creating worker worker.list= [Thu Sep 06 18:26:17 2001] [jk_worker.c (138)]: Into wc_create_worker [Thu Sep 06 18:26:17 2001] [jk_worker.c (152)]: wc_create_worker, about to create instance worker.list= of ajp12 [Thu Sep 06 18:26:17 2001] [jk_ajp12_worker.c (264)]: Into ajp12_worker_factory [Thu Sep 06 18:26:17 2001] [jk_worker.c (161)]: wc_create_worker, about to validate and init worker.list= [Thu Sep 06 18:26:17 2001] [jk_ajp12_worker.c (182)]: Into jk_worker_t::validate [Thu Sep 06 18:26:17 2001] [jk_ajp12_worker.c (194)]: In jk_worker_t::validate for worker worker.list= contact is localhost:8007 [Thu Sep 06 18:26:17 2001] [jk_worker.c (177)]: wc_create_worker, done [Thu Sep 06 18:26:17 2001] [jk_worker.c (223)]: build_worker_map, removing old worker.list= worker [Thu Sep 06 18:26:17 2001] [jk_worker.c (213)]: build_worker_map, creating worker ajp12-01 [Thu Sep 06 18:26:17 2001] [jk_worker.c (138)]: Into wc_create_worker [Thu Sep 06 18:26:17 2001] [jk_worker.c (152)]: wc_create_worker, about to create instance ajp12-01 of ajp12 [Thu Sep 06 18:26:17 2001] [jk_ajp12_worker.c (264)]: Into ajp12_worker_factory [Thu Sep 06 18:26:17 2001] [jk_worker.c (161)]: wc_create_worker, about to validate and init ajp12-01 [Thu Sep 06 18:26:17 2001] [jk_ajp12_worker.c (182)]: Into jk_worker_t::validate [Thu Sep 06 18:26:17 2001] [jk_ajp12_worker.c (194)]: In jk_worker_t::validate for worker ajp12-01 contact is localhost:9007 [Thu Sep 06 18:26:17 2001] [jk_worker.c (177)]: wc_create_worker, done [Thu Sep 06 18:26:17 2001] [jk_worker.c (223)]: build_worker_map, removing old ajp12-01 worker [Thu Sep 06 18:26:17 2001] [jk_worker.c (213)]: build_worker_map, creating worker ajp12-02 [Thu Sep 06 18:26:17 2001] [jk_worker.c (138)]: Into wc_create_worker [Thu Sep 06 18:26:17 2001] [jk_worker.c (152)]: wc_create_worker, about to create instance ajp12-02 of ajp12 [Thu Sep 06 18:26:17 2001] [jk_ajp12_worker.c (264)]: Into ajp12_worker_factory [Thu Sep 06 18:26:17 2001] [jk_worker.c (161)]: wc_create_worker, about to validate and init ajp12-02 [Thu Sep 06 18:26:17 2001] [jk_ajp12_worker.c (182)]: Into jk_worker_t::validate [Thu Sep 06 18:26:17 2001] [jk_ajp12_worker.c (194)]: In jk_worker_t::validate for worker ajp12-02 contact is localhost:9017 [Thu Sep 06 18:26:17 2001] [jk_worker.c (177)]: wc_create_worker, done [Thu Sep 06 18:26:17 2001] [jk_worker.c (223)]: build_worker_map, removing old ajp12-02 worker [Thu Sep 06 18:26:17 2001] [jk_worker.c (213)]: build_worker_map, creating worker ajp13-01 [Thu Sep 06 18:26:17 2001] [jk_worker.c (138)]: Into wc_create_worker [Thu Sep 06 18:26:17 2001] [jk_worker.c (152)]: wc_create_worker, about to create instance ajp13-01 of ajp13 [Thu Sep 06 18:26:17 2001] [jk_ajp13_worker.c (882)]: Into ajp13_worker_factory [Thu Sep 06 18:26:17 2001] [jk_worker.c (161)]: wc_create_worker, about to validate and init ajp13-01 [Thu Sep 06 18:26:17 2001] [jk_ajp13_worker.c (412)]: Into jk_worker_t::validate [Thu Sep 06 18:26:17 2001] [jk_ajp13_worker.c (425)]: In jk_worker_t::validate for worker ajp13-01 contact is localhost:9009 [Thu Sep 06 18:26:17 2001] [jk_ajp13_worker.c (451)]: Into jk_worker_t::init [Thu Sep 06 18:26:17 2001] [jk_worker.c (177)]: wc_create_worker, done [Thu Sep 06 18:26:17 2001] [jk_worker.c (223)]: build_worker_map, removing old ajp13-01 worker [Thu Sep 06 18:26:17 2001] [jk_worker.c (213)]: build_worker_map, creating worker ajp13-02 and one ajp13-02 on port 9019 My questions: 1.) Why gets this hardcoded worker on port 8007 created? 2.) Is this a Bug I shall report? Since I have a work around by putting this space in front of my first worker, I can live with this. Is this a Bug I should put into Bigzilla? Hans
RE: worker.properties swallows my first worker (mod_jk)
Hi Hans, The answers to your questions are: 1.) Why gets this hardcoded worker on port 8007 created? Don't know, I will investigate. 2.) Is this a Bug I shall report? Yes, and please attache the workers.properties in question. Thanks. Larry -Original Message- From: Hans Schmid [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 06, 2001 12:57 PM To: Tomcat-User Subject: worker.properties swallows my first worker (mod_jk) Hello, This is about mod_jk in Tomcat 3.3b1 on Solaris with Apache 1.3.19 It seems to me that the first worker found in the worker.list always gets created as ajp12 on port 8007 regardless what i configure. The following worker.list entry worker.list=worker.list=ajp12-01, ajp12-02, ajp13-01, ajp13-02 produces 4 workers: ajp12-01 on port 8007 ajp12 ajp12-02 on port 9017 ajp12 ajp13-01 on port 9009 ajp13 ajp13-02 on port 9019 ajp13 instead of the expected: ajp12-01 on port 9007 ajp12 ajp12-02 on port 9017 ajp12 ajp13-01 on port 9009 ajp13 ajp13-02 on port 9019 ajp13 Please note the ajp12-01 worker points to port 8007 instead of 9007. When I put a space in front of the first worker I get my expected 4 workers pointing to the correct ports plus a 5th worker ('' on port 8007) The following entry in workers.properties worker.list=worker.list= ajp12-01, ajp12-02, ajp13-01, ajp13-02 produces 5 workers instead of 4 Please note the port 8007 for the first worker named worker.list= of ajp12 I do not have a worker assigned to this port (greped through all config files). [Thu Sep 06 18:26:17 2001] [jk_worker.c (207)]: Into build_worker_map, creating 5 workers [Thu Sep 06 18:26:17 2001] [jk_worker.c (213)]: build_worker_map, creating worker worker.list= [Thu Sep 06 18:26:17 2001] [jk_worker.c (138)]: Into wc_create_worker [Thu Sep 06 18:26:17 2001] [jk_worker.c (152)]: wc_create_worker, about to create instance worker.list= of ajp12 [Thu Sep 06 18:26:17 2001] [jk_ajp12_worker.c (264)]: Into ajp12_worker_factory [Thu Sep 06 18:26:17 2001] [jk_worker.c (161)]: wc_create_worker, about to validate and init worker.list= [Thu Sep 06 18:26:17 2001] [jk_ajp12_worker.c (182)]: Into jk_worker_t::validate [Thu Sep 06 18:26:17 2001] [jk_ajp12_worker.c (194)]: In jk_worker_t::validate for worker worker.list= contact is localhost:8007 [Thu Sep 06 18:26:17 2001] [jk_worker.c (177)]: wc_create_worker, done [Thu Sep 06 18:26:17 2001] [jk_worker.c (223)]: build_worker_map, removing old worker.list= worker [Thu Sep 06 18:26:17 2001] [jk_worker.c (213)]: build_worker_map, creating worker ajp12-01 [Thu Sep 06 18:26:17 2001] [jk_worker.c (138)]: Into wc_create_worker [Thu Sep 06 18:26:17 2001] [jk_worker.c (152)]: wc_create_worker, about to create instance ajp12-01 of ajp12 [Thu Sep 06 18:26:17 2001] [jk_ajp12_worker.c (264)]: Into ajp12_worker_factory [Thu Sep 06 18:26:17 2001] [jk_worker.c (161)]: wc_create_worker, about to validate and init ajp12-01 [Thu Sep 06 18:26:17 2001] [jk_ajp12_worker.c (182)]: Into jk_worker_t::validate [Thu Sep 06 18:26:17 2001] [jk_ajp12_worker.c (194)]: In jk_worker_t::validate for worker ajp12-01 contact is localhost:9007 [Thu Sep 06 18:26:17 2001] [jk_worker.c (177)]: wc_create_worker, done [Thu Sep 06 18:26:17 2001] [jk_worker.c (223)]: build_worker_map, removing old ajp12-01 worker [Thu Sep 06 18:26:17 2001] [jk_worker.c (213)]: build_worker_map, creating worker ajp12-02 [Thu Sep 06 18:26:17 2001] [jk_worker.c (138)]: Into wc_create_worker [Thu Sep 06 18:26:17 2001] [jk_worker.c (152)]: wc_create_worker, about to create instance ajp12-02 of ajp12 [Thu Sep 06 18:26:17 2001] [jk_ajp12_worker.c (264)]: Into ajp12_worker_factory [Thu Sep 06 18:26:17 2001] [jk_worker.c (161)]: wc_create_worker, about to validate and init ajp12-02 [Thu Sep 06 18:26:17 2001] [jk_ajp12_worker.c (182)]: Into jk_worker_t::validate [Thu Sep 06 18:26:17 2001] [jk_ajp12_worker.c (194)]: In jk_worker_t::validate for worker ajp12-02 contact is localhost:9017 [Thu Sep 06 18:26:17 2001] [jk_worker.c (177)]: wc_create_worker, done [Thu Sep 06 18:26:17 2001] [jk_worker.c (223)]: build_worker_map, removing old ajp12-02 worker [Thu Sep 06 18:26:17 2001] [jk_worker.c (213)]: build_worker_map, creating worker ajp13-01 [Thu Sep 06 18:26:17 2001] [jk_worker.c (138)]: Into wc_create_worker [Thu Sep 06 18:26:17 2001] [jk_worker.c (152)]: wc_create_worker, about to create instance ajp13-01 of ajp13 [Thu Sep 06 18:26:17 2001] [jk_ajp13_worker.c (882)]: Into ajp13_worker_factory [Thu Sep 06 18:26:17 2001] [jk_worker.c (161)]: wc_create_worker, about to validate and init ajp13-01 [Thu Sep 06 18:26:17 2001] [jk_ajp13_worker.c (412)]: Into jk_worker_t::validate [Thu Sep 06 18:26:17 2001] [jk_ajp13_worker.c (425)]: In jk_worker_t::validate for worker ajp13-01 contact is localhost:9009 [Thu Sep 06 18:26
worker.properties
Hello, i did not edit my worker.properties file at all. I`m using Tomcat 3.2.1. It is working with Apache and in standalone mode (besides that session tracking, using URL rewritting is not working, which is another issue). Anyway, I was wondering if I have to edit this file. For example I see in the file that the workers.tomcat_home and the workers.java_home is not set correclty, as it is configured for the windows plattform. Nevertheless, tomcat is starting up and working, so I was just wondering if that is normal ? Here is my workers file... # ... skipped header comments ... # # workers.tomcat_home should point to the location where you # installed tomcat. This is where you have your conf, webapps and lib # directories. # workers.tomcat_home=c:\jakarta-tomcat # # workers.java_home should point to your Java installation. Normally # you should have a bin and lib directories beneath it. # workers.java_home=c:\jdk1.2.2 # # You should configure your environment slash... ps=\ on NT and / on UNIX # and maybe something different elsewhere. # ps=\ # ps=/ # #-- ADVANCED MODE #- # # #-- DEFAULT worket list -- #- # # # The workers that your plugins should create and work with # worker.list=ajp12, ajp13 # #-- DEFAULT ajp12 WORKER DEFINITION -- #- # # # Defining a worker named ajp12 and of type ajp12 # Note that the name and the type do not have to match. # worker.ajp12.port=8007 worker.ajp12.host=localhost worker.ajp12.type=ajp12 # # Specifies the load balance factor when used with # a load balancing worker. # Note: # lbfactor must be 0 # Low lbfactor means less work done by the worker. worker.ajp12.lbfactor=1 # #-- DEFAULT ajp13 WORKER DEFINITION -- #- # # # Defining a worker named ajp13 and of type ajp13 # Note that the name and the type do not have to match. # worker.ajp13.port=8009 worker.ajp13.host=localhost worker.ajp13.type=ajp13 # # Specifies the load balance factor when used with # a load balancing worker. # Note: # lbfactor must be 0 # Low lbfactor means less work done by the worker. worker.ajp13.lbfactor=1 # # Specify the size of the open connection cache. #worker.ajp13.cachesize # #-- DEFAULT LOAD BALANCER WORKER DEFINITION -- #- # # # The loadbalancer (type lb) workers perform wighted round-robin # load balancing with sticky sessions. # Note: # If a worker dies, the load balancer will check its state #once in a while. Until then all work is redirected to peer #workers. worker.loadbalancer.type=lb worker.loadbalancer.balanced_workers=ajp12, ajp13 # #-- DEFAULT JNI WORKER DEFINITION- #- # # # Defining a worker named inprocess and of type jni # Note that the name and the type do not have to match. # worker.inprocess.type=jni # #-- CLASSPATH DEFINITION - #- # # # Additional class path components. # worker.inprocess.class_path=$(workers.tomcat_home)$(ps)classes # # The XML parser provided with Tomcat # worker.inprocess.class_path=$(workers.tomcat_home)$(ps)lib$(ps)jaxp.jar worker.inprocess.class_path=$(workers.tomcat_home)$(ps)lib$(ps)parser.jar # # Tomcat's implementation # worker.inprocess.class_path=$(workers.tomcat_home)$(ps)lib$(ps)jasper.jar worker.inprocess.class_path=$(workers.tomcat_home)$(ps)lib$(ps)servlet.jar worker.inprocess.class_path=$(workers.tomcat_home)$(ps)lib$(ps)webserver.jar # # Javac as available from Java2SE # worker.inprocess.class_path=$(workers.java_home)$(ps)lib$(ps)tools.jar # # Setting the command line for tomcat # Note: The cmd_line string may not contain spaces. # worker.inprocess.cmd_line=-config worker.inprocess.cmd_line=$(workers.tomcat_home)/conf/jni_server.xml worker.inprocess.cmd_line=-home worker.inprocess.cmd_line=$(workers.tomcat_home) # # The JVM that we are about to use # # This is for Java2 # worker.inprocess.jvm_lib=$(workers.java_home)$(ps)jre$(ps)bin$(ps)classic$(p s)jvm.dll # # And this is for jdk1.1.X # #worker.inprocess.jvm_lib=$(workers.java_home)$(ps)bin$(ps)javai.dll # # # Setting the place for the stdout and stderr of tomcat # worker.inprocess.stdout=$(workers.tomcat_home)$(ps)inprocess.stdout worker.inprocess.stderr=$(workers.tomcat_home)$(ps)inprocess.stderr # # Setting the tomcat.home Java property # worker.inprocess.sysprops=tomcat.home
Re: worker.properties
Yes, you'll have to change this file. "Tassilo Pilati" [EMAIL PROTECTED] on 04/18/2001 08:47:11 AM Please respond to [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: (bcc: Geofferey G Chen/Corporate/Allianz Canada Inc.) Subject: worker.properties Fax to: Hello, i did not edit my worker.properties file at all. I`m using Tomcat 3.2.1. It is working with Apache and in standalone mode (besides that session tracking, using URL rewritting is not working, which is another issue). Anyway, I was wondering if I have to edit this file. For example I see in the file that the workers.tomcat_home and the workers.java_home is not set correclty, as it is configured for the windows plattform. Nevertheless, tomcat is starting up and working, so I was just wondering if that is normal ? Here is my workers file... # ... skipped header comments ... # # workers.tomcat_home should point to the location where you # installed tomcat. This is where you have your conf, webapps and lib # directories. # workers.tomcat_home=c:\jakarta-tomcat # # workers.java_home should point to your Java installation. Normally # you should have a bin and lib directories beneath it. # workers.java_home=c:\jdk1.2.2 # # You should configure your environment slash... ps=\ on NT and / on UNIX # and maybe something different elsewhere. # ps=\ # ps=/ # #-- ADVANCED MODE #- # # #-- DEFAULT worket list -- #- # # # The workers that your plugins should create and work with # worker.list=ajp12, ajp13 # #-- DEFAULT ajp12 WORKER DEFINITION -- #- # # # Defining a worker named ajp12 and of type ajp12 # Note that the name and the type do not have to match. # worker.ajp12.port=8007 worker.ajp12.host=localhost worker.ajp12.type=ajp12 # # Specifies the load balance factor when used with # a load balancing worker. # Note: # lbfactor must be 0 # Low lbfactor means less work done by the worker. worker.ajp12.lbfactor=1 # #-- DEFAULT ajp13 WORKER DEFINITION -- #- # # # Defining a worker named ajp13 and of type ajp13 # Note that the name and the type do not have to match. # worker.ajp13.port=8009 worker.ajp13.host=localhost worker.ajp13.type=ajp13 # # Specifies the load balance factor when used with # a load balancing worker. # Note: # lbfactor must be 0 # Low lbfactor means less work done by the worker. worker.ajp13.lbfactor=1 # # Specify the size of the open connection cache. #worker.ajp13.cachesize # #-- DEFAULT LOAD BALANCER WORKER DEFINITION -- #- # # # The loadbalancer (type lb) workers perform wighted round-robin # load balancing with sticky sessions. # Note: # If a worker dies, the load balancer will check its state #once in a while. Until then all work is redirected to peer #workers. worker.loadbalancer.type=lb worker.loadbalancer.balanced_workers=ajp12, ajp13 # #-- DEFAULT JNI WORKER DEFINITION- #- # # # Defining a worker named inprocess and of type jni # Note that the name and the type do not have to match. # worker.inprocess.type=jni # #-- CLASSPATH DEFINITION - #- # # # Additional class path components. # worker.inprocess.class_path=$(workers.tomcat_home)$(ps)classes # # The XML parser provided with Tomcat # worker.inprocess.class_path=$(workers.tomcat_home)$(ps)lib$(ps)jaxp.jar worker.inprocess.class_path=$(workers.tomcat_home)$(ps)lib$(ps)parser.jar # # Tomcat's impl
Re: worker.properties
The workers.properties file configures the worker threads that take requests for servlets/jsp's from apache and processes them appropirately. As such, when running Tomcat without Apache it will have no effect. You only need to edit this file when you run Apache and Tomcat together. Infact you'll get a syntax error on a non-PC platform if you forget to edit this file and try and include it in the Apache directives. See the workers.properties howto for more information (its in the Tomcat docs somewhere). sam - Original Message - From: "Tassilo Pilati" [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, April 18, 2001 1:47 PM Subject: worker.properties Hello, i did not edit my worker.properties file at all. I`m using Tomcat 3.2.1. It is working with Apache and in standalone mode (besides that session tracking, using URL rewritting is not working, which is another issue). Anyway, I was wondering if I have to edit this file. For example I see in the file that the workers.tomcat_home and the workers.java_home is not set correclty, as it is configured for the windows plattform. Nevertheless, tomcat is starting up and working, so I was just wondering if that is normal
AW: worker.properties
Well, this file is in the conf directory of my tomcat installation. But I don`t get an error message -Ursprngliche Nachricht- Von: Sam Newman [mailto:[EMAIL PROTECTED]] Gesendet: Mittwoch, 18. April 2001 15:36 An: [EMAIL PROTECTED] Betreff: Re: worker.properties The workers.properties file configures the worker threads that take requests for servlets/jsp's from apache and processes them appropirately. As such, when running Tomcat without Apache it will have no effect. You only need to edit this file when you run Apache and Tomcat together. Infact you'll get a syntax error on a non-PC platform if you forget to edit this file and try and include it in the Apache directives. See the workers.properties howto for more information (its in the Tomcat docs somewhere). sam - Original Message - From: "Tassilo Pilati" [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, April 18, 2001 1:47 PM Subject: worker.properties Hello, i did not edit my worker.properties file at all. I`m using Tomcat 3.2.1. It is working with Apache and in standalone mode (besides that session tracking, using URL rewritting is not working, which is another issue). Anyway, I was wondering if I have to edit this file. For example I see in the file that the workers.tomcat_home and the workers.java_home is not set correclty, as it is configured for the windows plattform. Nevertheless, tomcat is starting up and working, so I was just wondering if that is normal