The mod_jk.so was compiled with an apache using EAPI (mod_ssl).
And your apache didn't use such API.
You could see soon at http://rpmized.free.fr/ the announce
of tomcat 3.2 & tomcat-mod 3.2 RPM ;-)
"Pour la plupart des hommes, se corriger consiste � changer de d�fauts."
-- Voltaire
>-----Original Message-----
>From: Phillip T. Gerringer [mailto:[EMAIL PROTECTED]]
>Sent: Thursday, November 30, 2000 2:20 PM
>To: [EMAIL PROTECTED]
>Subject: Re: mod_jk.so problem on Linux
>
>
>I know this is going to help very little but... Apparently
>when you get
>the garbled message, it means the module was compiled with different
>options than the calling module. I know that is basic but
>that is where I
>would start. Example: if your Apache has SSL enabled, then you must
>compile mod_jk with the SSL module.
>
>Hope that helps...
>
>On Thu, 30 Nov 2000, Graham Freeman wrote:
>
>> I am having trouble getting mod_jk.so working in Apache 1.3
>on my Linux box.
>> If I include the instruction
>>
>> LoadModule jk_module libexec/mod_jk.so
>>
>> in my httpd.conf file, Apache reports
>>
>> # ./bin/apachectl configtest
>> Syntax error on line 991 of /usr/local/apache/conf/httpd.conf:
>> API module structure `jk_module' in file
>/usr/local/apache/libexec/mod_jk.so is garbled - perhaps this
>is not an Apache module DSO?
>>
>> I have tried recompiling the library from the source, and I
>get a different
>> file length for mod_jk.so (88757) but no change in the behaviour.
>> I also tried using mod_jk.conf-auto, but it contains the
>same LoadModule
>> instruction and gives the same error.
>>
>> Tomcat 3.2-b8 is otherwise working fine stand-alone.
>>
>> Graham
>>
>
