Without looking at the code, I believe that this is only caused when the 'JkWorkersFile' no longer points to the correct place in your httpd.conf (or included file). It can also be caused if the file can't be read from the Apache user (On RedHat, defaults to 'apache', in the download defaults to 'nobody').
You are very brave to still be running Apache 1.3.9 :). "Dayo Oliyide" <[EMAIL PROTECTED]> wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > > I'm currently having problems getting Apache to use load mod_jk, it keeps giving this error "[emerg] Error while opening the workers". The workers.properties file exists and has the right attributes. I'm using Tomcat 3.3.1, Apache 1.3.9 and mod_jk-3.3-ap13-noeapi.so with Sun's jdk 1.4(build 1.4.0_02-b02) on linux (2.2.12-20). > > Everything used to work okay the only change I've made is to Web app and its logic, it used to run using Apache, tomcat and jonas but now uses just Apache and tomcat. I can't understand how this could affect the mod_jk. > > Thanks for any help > > Dayo > > > > --------------------------------- > Do you Yahoo!? > Yahoo! Mail Plus - Powerful. Affordable. Sign up now -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
