I did.
I did it again. The error was different this time. Similar error with a
different variable name.
If the compilation isn't complete, why do I see mod_jk.so?
Anyways, I got away with this by downloading a binary version, which again
was not working earlier. And suddenly it did. It's highly unpredictable.
I can just hope that I have a good luck, not to see this happen again.

-----Original Message-----
From: GOMEZ Henri [mailto:[EMAIL PROTECTED]]
Sent: Monday, July 02, 2001 2:22 PM
To: [EMAIL PROTECTED]
Subject: RE: variable jk_b_set_buffer_size in mod_jk module....


You didn't compile ALL the source files

-
Henri Gomez                 ___[_]____
EMAIL : [EMAIL PROTECTED]        (. .)
PGP KEY : 697ECEDD    ...oOOo..(_)..oOOo...
PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6



>-----Original Message-----
>From: Anshul [mailto:[EMAIL PROTECTED]]
>Sent: Saturday, June 30, 2001 7:20 AM
>To: [EMAIL PROTECTED]
>Subject: variable jk_b_set_buffer_size in mod_jk module....
>
>
>I built mod_jk.so from the source code. But now when I am
>adding this one in
>apache, it doesn't start, I mean apache.
>I get the following
>
>Syntax error on line 131 of /etc/httpd/conf/httpd.conf:
>Cannot load /etc/httpd/modules/mod_jk.so into server:
>/etc/httpd/modules/mod_jk.so: undefined symbol: jk_b_set_buffer_size
>
>Someone please help me...........
>
>-----Original Message-----
>From: Anshul [mailto:[EMAIL PROTECTED]]
>Sent: Saturday, June 30, 2001 10:00 AM
>To: [EMAIL PROTECTED]
>Subject: mod_jk.so-eapi
>
>
>Why do I see these in
>http://jakarta.apache.org/builds/jakarta-tomcat/release/v3.2.2/
bin/linux/i38
6/ ????

I am looking for mod_jk.so.
There are these files
 mod_jk.so-eapi
 mod_jk.so-eapi.asc
 mod_jk.so-noeapi
 mod_jk.so-noeapi.asc

Does that mean mod_jk.so changed? But I don't see any documentation about
this one.

I am having problem integrating apache with tomcat. Apache doesn't delegate
the servlet jsp/request to tomcat. It just trys to serv it on it's own.
Anyone any clues??????
Thanks in advance,
Anshul

Reply via email to