Kudos!
That worked pretty well. I had to modify my Listener directives to pickup the different location of mod_jk.so (modules/mod_jk.so instead of libexec/mod_jk.so) but other than that, it worked like a charm. I'll update my How-To as soon as I can, with props to you for the tip (I won't post your email address, though). Thanks Mark. John Turner [EMAIL PROTECTED] -----Original Message----- From: Sullivan, Mark E [mailto:[EMAIL PROTECTED]] Sent: Tuesday, August 20, 2002 9:32 AM To: 'Tomcat Users List' Subject: RE: BAD packet - Apache 2.0.39 + mod_jk (or mod_webapp) on linux Sorry, my mistake. I misread your email. Now that i think about it some more, i didn't use ant to build the connector. These are the steps i followed cd /home/mark/jakarta-tomcat-connectors-4.1.9-src/jk/native ./buildconf.sh ./configure --with-apxs=/usr/local/apache2/bin/apxs make make install The --with-apxs command ensures that the module is built for the correct version of apache, using that version's own apxs script. Assuming no errors occur, the jk module should have been put into your apache/modules directory. > -----Original Message----- > From: Turner, John [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, August 20, 2002 8:29 AM > To: 'Tomcat Users List' > Subject: RE: BAD packet - Apache 2.0.39 + mod_jk (or mod_webapp) on > linux > > > > It's true. > > There are two different apache directories in the connectors tree: > apache-1.3 and apache-2.0. My How-To only details building > in apache-1.3. > "ap_table_get" is an Apache 1.3 API function, so to get > mod_jk to work with > Apache 2.0.39/40 requires something different that what is > currently in my > How-To. > > I'm not saying definitively that mod_jk doesn't work with > apache 2 (I don't > see why it wouldn't), just that I haven't figured it out yet > myself, and > haven't updated my document, which folks seem to be using. > I'm trying to > avoid people wasting their time by relying on my document in > a scenario it > doesn't support yet. > > John Turner > [EMAIL PROTECTED] > > -----Original Message----- > From: Sullivan, Mark E [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, August 20, 2002 9:18 AM > To: 'Tomcat Users List' > Subject: RE: BAD packet - Apache 2.0.39 + mod_jk (or mod_webapp) on > linux > > > That's not necessarily true. I'm running mod_jk on rh 7.3 > with apache 2.0.39 > and tomcat 4+. I had no problems building or using the module. I don't > remember having to do anything special when building the > module either. > > > -----Original Message----- > > From: Turner, John [mailto:[EMAIL PROTECTED]] > > Sent: Tuesday, August 20, 2002 8:08 AM > > To: 'Tomcat Users List' > > Subject: RE: BAD packet - Apache 2.0.39 + mod_jk (or mod_webapp) on > > linux > > > > > > > > I just built apache 2.0.40 and tried to get it working with > > mod_jk.so on RH > > 7.2. No luck...the mod_jk.so file that works with 1.3.26 is > > not compatible > > with 2.0.40. The error message I get is: > > > > Cannot load /usr/local/apache2/lib/mod_jk.so into server: > > /usr/local/apache2/lib/mod_jk.so: undefined symbol: ap_table_get > > > > So, right off the bat, I can tell you that the instructions > > in my How-To > > will only work with apache 1.3.26, not 2.0.39/40. I will > > have to research > > if it is a do-or-die problem with mod_jk (which means > > switching to mod_jk2), > > or just a rebuild of mod_jk with options that allow use with apache > > 2.0.39/40. > > > > John Turner > > > > -----Original Message----- > > From: Turner, John [mailto:[EMAIL PROTECTED]] > > Sent: Tuesday, August 20, 2002 8:15 AM > > To: 'Tomcat Users List' > > Subject: RE: BAD packet - Apache 2.0.39 + mod_jk (or mod_webapp) on > > linux > > > > > > > > I notice you mentioned that you had copied the JAR files to > > CATALINA_HOME/common after building the connector. This is > > one area that > > confuses me about connecting apache to tomcat with mod_jk. > > The docs I read > > told me to build those JARs, but I don't have them anywhere in my > > CATALINA_HOME tree, I left them in the source-build > > directory. As far as I > > can tell, they aren't needed. > > > > This might be the problem, or, if it isn't, did you find a resource > > someplace that explained what the JAR files are for, where > > they should go, > > and why? I didn't find one, and would be interested in reading it. > > > > My memory is hazy, too, but it seems to me that apache 2.x > > requires mod_jk2, > > not mod_jk. If I have a chance today I will build 2.0.39 > > from source and > > see if it works instead of 1.3.26 in my currently-working > > apache+tomcat+mod_jk environment. > > > > John Turner > > [EMAIL PROTECTED] > > > > > > -----Original Message----- > > From: Mathew Pole [mailto:[EMAIL PROTECTED]] > > Sent: Tuesday, August 20, 2002 3:28 AM > > To: '[EMAIL PROTECTED]' > > Subject: BAD packet - Apache 2.0.39 + mod_jk (or > mod_webapp) on linux > > > > > > Hi , > > > > At first glance the following combination sounded like a great idea > > (especially as I had success with this on windows 2000): > > tomcat 4.0.4 > > tomcat connectors 4.0.4 > > apache 2.0.39 > > linux (gentoo 1.2 distribution) > > In reality it has proved very challenging. I've tried the following: > > > > Following instructions provided by John Turner in > > http://www.johnturner.com/howto/apache-tomcat-howto.html, I > > came across a > > couple of issues which I resolved by > > failed trying to build the mod_jk.so, but after setting > > apache13.home to a > > bogus location and running ant native it appears to have worked > > copied jk/build/lib/mod_jk.so apache2/modules > > copied jk/build/lib/*.jar to tomcat/common > > updated apache.conf file as suggested > > updated server.xml as suggested, with addition of > > modJk="/usr/local/apache2/modules/mod_jk.so" in the listener > > definition > > Currently, in the tomcat/logs/catalina.out file the > following text is > > appearing (note the string after In : : [ changes, but 4/843 remains > > constant): > > > > BAD packet 256 > > In: : [B@3e58d4 4/843 > > > > followed by what appears to be some hex output of mainly 00s. > > > > My suspicion is that this error is caused by one of: > > mod_jk.so being compiled incorrectly > > connector jar files being compiled incorrectly or being in > > the wrong place > > incorrect configuration > > I've also attached logs & configuration files to this email. > > Hopefully this > > is enough information for someone to help me. > > > > In addition to this I looked at the instructions in > > http://wass.homelinux.net/howtos/Jakarta_How-To.shtml, but the > > mod-jk-303-ap20.so doesn't work with apache 2.0.39. > > > > > > > > Regards, > > Mathew > > -- > > Mathew Pole > > Web Architect, Gerard Industries > > email: [EMAIL PROTECTED] > > phone: 08 8269 0511 ext 313, fax: 08 8340 1212, mobile: 0403 164 617 > > > > -- > > 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]> > > -- > 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]> -- 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]>
