Barry,

make sure you have built the right jk module.

I've exactly the same config than you.
Redhat ES 3.0, apache 2.0.49 jk2 and jboss 3.2.3 that
comes with tomcat 3.2.3

my httpd.conf file  contains :
LoadModule jk2_module modules/mod_jk2.so
<IfModule mod_jk2.c>
JKSet config.file /opt/apachessl-2.0.49/inet/conf/workers2.properties
</IfModule>

the workers2 file may contains
[shm]
file=/var/log/apache/inet/jk2.shm
[channel.socket:localhost:8009]
port=8009
host=127.0.0.1

[ajp13:localhost:8009]
channel=channel.socket:localhost:8009

# Uri mapping

[uri:/apps/*]
worker=ajp13:localhost:8009

and it works fine.
_______________________________________________
NATEXIS ASSET MANAGEMENT
Meissa SAKHO
01 58 19 45 71. . . . . . . . . . . . (84571)
[EMAIL PROTECTED]




Barry Roberts <[EMAIL PROTECTED]>
25/05/2004 21:14
Veuillez r�pondre � "Tomcat Users List"


        Pour :  [EMAIL PROTECTED]
        cc :
        Objet : mod_jk error with Apache 2.0.49


I'm trying to get mod_jk working with apache 2.0.49 built from source on
RedHat ES 3.0.  I've got the module built and in the modules directory,
and my httpd.conf contains:

LoadModule jk_module modules/mod_jk.so

JkWorkersFile /usr/local/apache2/conf/workers.properties
JkLogFile /var/log/mod_jk.log
JkLogLevel debug
JkMount /apps/* xsappa
JkMount /admin xsappa

This is towards the top of the file outside of any <virtualhost> or
<directory> elements (I have also tried putting this at the bottom of
the file).

My workers.properties is:


worker.list=xsappa

worker.xsappa.port=139
worker.xsappa.host=192.168.2.42
worker.xsappa.type=ajp13
worker.xsappa.lbfactor=1

Every time I try to hit a servlet or jsp I get the following in my
mod_jk.log:
[Tue May 25 12:45:38 2004]  [jk_worker.c (136)]: wc_get_worker_for_name,
done did not found a worker

And of course a 500 in the browser.

The tomcat server works fine.  I can put jk2 into the web server and it
mostly works (I get "Broken Pipe" exceptions when I KNOW it's not a user
pressing cancel in the browser, but that's another issue).  I can hit
the tomcat server on port 8080 and it's just fine.

I can't use jk2 because of the spurious broken pipes, and now I can't
get jk1 working at all.  I have this suspicion that I'm missing
something obvious, but I can't find it.

Any help would be greatly appreciated.

Thanks,
Barry Roberts


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





L'integrite de ce message n'etant pas assuree sur internet, Natexis
Banques Populaires ne peut etre tenu responsable de
son contenu. Toute utilisation ou diffusion non autorisee est
interdite. Si vous n'etes pas destinataire de ce message, merci de le
detruire et d'avertir l'expediteur.

The integrity of this message cannot be guaranteed
on the Internet. Natexis Banques Populaires can not therefore be
considered responsible for the contents.Any unauthorized use or dissemination is 
prohibited.
If you are not the intended recipient of this message, then please delete it and
notify the sender.

Reply via email to