If the naming of these files follows the usual conventions - mod_jk2.dll
is a library for Windows, mod_jk2.so is a library for unix/linux.
They're probably equivalents to eachother but will not be interchangable.
--
Stephen
Hirode, Kartheek V. wrote:
Hello all
We have the following config working hunky-dory in our env:
- Win2000
- Apache 2.0.47 (port 80)
- Tomcat 4.1.16 (port 8009)
- jk2
- The three run inprocess as an NT service
- The jk2 starts the Tomcat with the JNI APR (TomcatStarter)
Everything works fine.
Now here's the problem:
- The jk2 module is a DLL (mod_jk2.dll)
- Based on certain recommendations, we are trying to change this to use the
mod_jk2.so version.
So what we've done is:
- Replaced the DLL with the SO file
- Changed the LoadModule directive in the httpd.conf file to point to the SO
file
- Restarted the NT service
- The loading of the module works fine, no errors
- But the calls to Tomcat do not work. In fact, Tomcat has not even started
We get the following errors when a call is made that needs the JK2 and Tomcat:
[Mon Jul 19 12:44:11 2004] [error] channelApr.open() attempt to connect to
127.0.0.1:8009 (localhost) failed 730061
[Mon Jul 19 12:44:11 2004] [error] ajp13.connect() failed ajp13:localhost:8009
[Mon Jul 19 12:44:11 2004] [error] ajp13.service() failed to connect endpoint
errno=0 No error
[Mon Jul 19 12:44:11 2004] [error] ajp13.service() Error forwarding
ajp13:localhost:8009 1 1
[Mon Jul 19 12:44:11 2004] [error] mod_jk2.handler() Error connecting to
tomcat 12, status 0
From RTFM, I know that there are several configurations in play here, but they all
seem to apply when an Apache-jk2-Tomcat needs to be configured from ground up. What we
have in our case is a config that works fine with the DLL file, but does NOT work at
all with the SO file.
Any pointers?
Thanks and regards
-- Kartheek Hirode
Hewlett Packard
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
