[JBoss-user] (no subject)

[Finn, Michael]

I seem to be unable to get mod_jk2 talking to Jetty. I built mod_jk2 from source (jakarta-tomcat-connectors-4.1.18), and have it config'd on Apache 2.0.44 (RH 7.2). JBoss 3.2.0 built from JBoss 3.2 branch running on W2K. I have workers2.properties config'd. In the docs, I saw reference to jk.properties on the Tomcat side, but see no analog to it in Jetty. One of the errors I get is what looks to be missing shared mem file (even though I am not using UNIX domain sockets, so I am not sure how that applies), which is config'd in jk2.properties - makes me wonder if I'm missing something.

When I access a mapped application, I get below in error_log (startup log stuff is included as well). Browser gets a 500. workers2.properties is below as well.
No mod_jk log. Jetty AJP is listening on 8009.

TIA,
Mike

error_log
[Mon Mar 24 09:12:08 2003] [notice] Apache/2.0.44 (Unix) DAV/2 mod_jk2/2.0.3-dev configured -- resuming normal operations
[Mon Mar 24 09:12:08 2003] [error] shm.init(): No file
[Mon Mar 24 09:12:14 2003] [error] workerEnv.init() create slot epStat.0 failed
[Mon Mar 24 09:12:14 2003] [error] mod_jk.handler() Error connecting to tomcat 120000

workers2.properties:

[channel.socket:mjf860-1:8009]
port=8009
host=10.160.73.98

[ajp13:mjf860-1:8009]
channel=channel.socket:mjf860-1:8009

[uri:/apps/*]
worker=ajp13:mjf860-1:8009

 

-----------------------
Mike Finn                              
Frontier Communications     
Rochester, NY                   
V: 585-777-8202
E: mailto:[EMAIL PROTECTED]