Faine, Mark wrote:
Apache 2.0.43
mod_jk2 2.0.0
Tomcat 4.0.6
Can't get socket to work, I get this error message:
Is this the log from apache or tomcat?
[Mon Jan 13 14:43:21 2003] [notice] Apache/2.0.43 (Unix) mod_ssl/2.0.43
OpenSSL/0.9.6g DAV/2 mod_jk2/2.0.0 configured -- resuming normal operations
[Mon Jan 13 14:43:39 2003] [error] channelUn.connect() connect failed 2 No
such file or directory
[Mon Jan 13 14:43:39 2003] [error] ajp13.connect() failed
ajp13:/usr/local/tomcat/logs/jk2.socket
[Mon Jan 13 14:43:39 2003] [error] ajp13.service() failed to connect
endpoint errno=2 No such file or directory
[Mon Jan 13 14:43:39 2003] [error] ajp13.service() Error forwarding
ajp13:/usr/local/tomcat/logs/jk2.socket 1 1
[Mon Jan 13 14:43:39 2003] [error] mod_jk.handler() Error connecting to
tomcat 120000
Is the socket supposed to be created automatically on the fly? (upon
starting of server)
I believe so. When run tomcat does tomcat create/use the socket? I've
had trouble in the past getting the channelUnix socket to work -- was
related to the ClassLoaders not functioning properly on Solaris 8
(Apache 2.0.40, Tomcat 4.1.15, mod_jk2 2.0.1). Because Tomcat couldn't
create the socket, Apache couldn't find it, so it couldn't use it.
My workers2.properties file and jk2.properties files are almost exact copies
of the common examples. I can post them anyway if it will help.
Also, Could ports blocked by the firewall cause any problems with
tomcat/apache integration and normal operation?
Any suggestions would be appreciated
Thanks,
Mark
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
