Hello GOMEZ Henri,
Everything is working great for me so this is not a call for help. Mandrake
7.2, as you mention, uses a modified version of Apache they call
Apache-AdvancedExtranetServer version 3.12 (SGI). I found that in using the
binary mod_jk from the Jakarta site that everything would configure
correctly and produce the message that Ajp13 worker found etc. All
indications in the logs were that it was working correctly, however, no
forwarding would take place. Adam Fowler mentioned that he had compiled a
version which works for Mandrake 7.2 and indeed it does. I am under the
impression, perhaps mistakenly so, that differences in the version of Apache
and even the Kernel can effect the mod_jk's performance and as such, it
should be rebuilt for every unique system. I believe this to be our (the
users) responsibility as there are so many variations with Linux.
I only see one version of mod_jk.so available for Linux on the Jakarta
site..? In hindsight, I believe that I have installed a Mandrake 7.2 with
Apache and Tomcat using the original binary and it worked fine. I'm fuzzy as
to whether that Apache had mod_ssl. Perhaps it was the ssl version that was
needed for my most recent install. (mod_jk.so-eapi)
I really appreciate your hard work with Tomcat. You and Craig McClanahan
are heroes here.
Best Regards,
Craig O'Brien
-----Original Message-----
From: GOMEZ Henri [mailto:[EMAIL PROTECTED]]
Sent: Friday, May 04, 2001 12:26 AM
To: [EMAIL PROTECTED]
Subject: RE: Apache and Tomcat integration
>You really need to build your own mod_jk for it to work. It will be
>different with nearly every system configuration. I use
>Mandrake 7.2 as
>well and the binary from Jakarta-Apache does not work with this system.
What's the problem with binary from Jakarta-Apache which didn't works
under Mandrake ?
I could tell you that the mod_jk.so you found at Jakarta-Apache are
built on Redhat 6.2 systems with latest apache 1.3.19. There is now
each time a mod_jk.so-eapi for those of us using EAPI (ie mod_ssl)
and mod_jk.so-stdapi (standard apache).
Mandrake use in their apache distrib the unsupported (by HTTPD team)
SGI patches which brake many others modules (ie mod_gzip).
But you could still rebuilt the mod_jk from source to make them
works on your specific system.
>Our friend Adam Fowler has built one for Mandrake 7.2 which
>works and you
>can get it at http://willow.cc.edu/docs/adminguide
>
>Regards,
>Craig
>
>-----Original Message-----
>From: Tarwinder Dhak [mailto:[EMAIL PROTECTED]]
>Sent: Tuesday, May 01, 2001 3:40 AM
>To: 'Tomcat'
>Subject: Apache and Tomcat integration
>
>
>Hi all,
>
>I'm trying to get apache and Tomcat 3.2.1 to talk to each other using
>mod_jk.so (downloaded from the internet, not compiled) with the ajp13
>protocol (on Mandrake 7.2). I've got Tomcat running as a
>stand alone web
>server executing servlets and jsp files. I've also got Apache
>loading the
>mod_jk.so module while using mod_jk.conf-auto file generated by tomcat.
>
>The problem I've got is that apache doesn't seem to be
>relaying any servlet
>or jsp requests to tomcat on port 8009. Instead it just tries
>to serve the
>pages as normal (I've been using the examples supplied by tomcat).
>
>I think tomcat is definitely listening on port 8009 because if
>I telnet or
>http request that port it does actually connect (using the netstat -l
>command).
>
>This is starting to drive me around the twist!!
>Any help would be gratefully appreciated.
>
>Regards
>
>Tarwinder Dhak
>[EMAIL PROTECTED]
>
>Transact Group
>Development
>
>Legal Disclaimer: Internet email communications are not secure and
>therefore the NetInvest Group does not accept legal responsibility for
>the contents of this message. Any views or opinions presented
>are solely
>those of the author and do not necessarily represent those of the
>NetInvest Group unless otherwise specifically stated.
>
>
