Re: Mod_Jk -- Latest CVS - FWIW
NormW wrote: Greetings! Thanks for the _very_ quick reply... you must also have problem keeping food out of the keyboard too... Just woke up 8-). Is it correct then that the worker list should also look like: JkWorkerProperty worker.worker.list=worker1,worker2 (?) No. Are you insinuating the documentation about formating directives? Feel free to write something more meaningful :) Also the worker.list if not present has default worker name 'ajp13'. So if you omit worker.list it's like worker.list=ajp13. Mladen. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Mod_Jk -- Latest CVS - FWIW
Mladen Turk wrote: NormW wrote: Look at: http://jakarta.apache.org/tomcat/connectors-doc/config/workers.html (Section: Defining Workers) The lines in question: JkWorkerProperty worker.list=worker1,worker2 # Worker1 JkWorkerProperty worker.worker1.type=ajp13 JkWorkerProperty worker.worker1.host=localhost JkWorkerProperty worker.worker1.port=9009 At the present time there are two workers [ajp13] defined but all URL's are aimed at worker1. If there is a bug in these then the parsing is not picking it up... Yes, that's true, cause the worker will not be created. Q. If the JkWorkersFile Directive is not used, is the module creating a default worker, or looking for a workers.properties file on its own initiative? No. There is no such thing as default worker. The workers.properties file is read only when declared with JkWorkersFile. Great! No 'Defaults' means the reposibility to get things right is with the admin, not the programmer in this regard. I would hope to see Mod_Jk fail at start if a Jk URL directive is encountered when no workers have been defined. That's why my first .conf JK directives are to create the workers. Url mappings are not attached to the worker. Actually url mapping (if positive one made) just picks up the worker name. Then the worker is found that must be listed in the 'worker.list' directive. If there is none, then the messages like you posted will emerge in the log file. I agree with you, that we have a problem with mod_jk not showing any error message in the config phase (when server is started). Like said before it'll have to wait until the next release. I have no problem with waiting, just with things not (seeming to) work, especially when NetWare is only a small fish... strangely enough, I did get it working a few times to the /manager/html/ page... Regards, Mladen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] . Greetings! Thanks for the _very_ quick reply... you must also have problem keeping food out of the keyboard too... Is it correct then that the worker list should also look like: JkWorkerProperty worker.worker.list=worker1,worker2 (?) Norm - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Mod_Jk -- Latest CVS - FWIW
NormW wrote: Look at: http://jakarta.apache.org/tomcat/connectors-doc/config/workers.html (Section: Defining Workers) The lines in question: JkWorkerProperty worker.list=worker1,worker2 # Worker1 JkWorkerProperty worker.worker1.type=ajp13 JkWorkerProperty worker.worker1.host=localhost JkWorkerProperty worker.worker1.port=9009 At the present time there are two workers [ajp13] defined but all URL's are aimed at worker1. If there is a bug in these then the parsing is not picking it up... Yes, that's true, cause the worker will not be created. Q. If the JkWorkersFile Directive is not used, is the module creating a default worker, or looking for a workers.properties file on its own initiative? No. There is no such thing as default worker. The workers.properties file is read only when declared with JkWorkersFile. I would hope to see Mod_Jk fail at start if a Jk URL directive is encountered when no workers have been defined. That's why my first .conf JK directives are to create the workers. Url mappings are not attached to the worker. Actually url mapping (if positive one made) just picks up the worker name. Then the worker is found that must be listed in the 'worker.list' directive. If there is none, then the messages like you posted will emerge in the log file. I agree with you, that we have a problem with mod_jk not showing any error message in the config phase (when server is started). Like said before it'll have to wait until the next release. Regards, Mladen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Mod_Jk -- Latest CVS - FWIW
Mladen Turk wrote: Mladen Turk wrote: NormW wrote: Greetings All, Just built the latest Mod_Jk from CVS with Apache2.1 on Win for NetWare, and with only the three 'mandatory' settings for worker1 of type, host and port, all I'm getting is "Internal Server Error", and the Jk logs do not show good signs of matching URL's to the worker1... You have a syntax error in the workers.properties. Just post those three lines :) Or perhaps you don't have a fourth line ? workers.list=worker1 Without that it will not work. Look at: http://jakarta.apache.org/tomcat/connectors-doc/config/workers.html (Section: Defining Workers) Mladen. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] . Greetings, The lines in question: JkWorkerProperty worker.list=worker1,worker2 # Worker1 JkWorkerProperty worker.worker1.type=ajp13 JkWorkerProperty worker.worker1.host=localhost JkWorkerProperty worker.worker1.port=9009 At the present time there are two workers [ajp13] defined but all URL's are aimed at worker1. If there is a bug in these then the parsing is not picking it up... Q. If the JkWorkersFile Directive is not used, is the module creating a default worker, or looking for a workers.properties file on its own initiative? I would hope to see Mod_Jk fail at start if a Jk URL directive is encountered when no workers have been defined. That's why my first .conf JK directives are to create the workers. Norm - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]