tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Eggers <its_toas...@yahoo.com>
Subject Re: Binary of mod_jk.so for Apache 2.2.x
Date Thu, 14 Jul 2011 17:21:46 GMT
----- Original Message -----

> From: "Leffingwell, Jonathan R CTR FRCSE, JAX 7.2.2" <jonathan.leffingwell.ctr@navy.mil>
> To: Tomcat Users List <users@tomcat.apache.org>
> Cc: 
> Sent: Thursday, July 14, 2011 10:08 AM
> Subject: RE: Binary of mod_jk.so for Apache 2.2.x
> 
> Chris, something DID just dawn on me...
> 
> I have my own account on that Linux server, though not with root access or 
> anything.  Would it be possible for me to compile mod_jk.so into my own space 
> and then tell him where the mod_jk.so is?  If so, would the following steps be 
> how I would generate mod_jk.so (and forgive the "newbie"ness of the 
> question, please)?
> 
> tar -xvzf tomcat-connectors-1.2.30-src.tar.gz
> 
> cd tomcat-connectors-1.2.30-src/native/ # which apxs 
> 
> ./configure --with-apxs=/usr/sbin/apxs --enable-api-compatibility 
> 
> make 
> 
> make install
> 
> 
> At this point, I think all I want to do is produce a functioning mod_jk.so and 
> let him put it into the modules directory.  Would this do it?
> 
> Thanks again!
> 
> JL
> 
> 
> -----Original Message-----
> From: Christopher Schultz [mailto:chris@christopherschultz.net] 
> Sent: Thursday, July 14, 2011 12:34 PM
> To: Tomcat Users List
> Subject: Re: Binary of mod_jk.so for Apache 2.2.x
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Leon,
> 
> On 7/12/2011 7:42 PM, Leon Kolchinsky wrote:
>>  Go to http://tomcat.apache.org/download-connectors.cgi and download
>>  the source code:
>> 
>>  # tar -xvzf tomcat-connectors-1.2.30-src.tar.gz
>> 
>>  Read docs/webserver_howto/apache.html or native/BUILDING.txt for
>>  options.
>> 
>>  # cd tomcat-connectors-1.2.30-src/native/ # which apxs # ./configure
>>  --with-apxs=/usr/sbin/apxs --enable-api-compatibility # make # make
>>  install
> 
> All that as root? Hmm.
> 
> Also, not everyone has a C compiler, especially on a production machine.
> (The answer, of course, is to build somewhere else and upload.)
> 
> Jonathan, I understand that you want convenience, but there are several
> factors to consider, here:
> 
> 1. Unless you download a binary from a trusted source (i.e. not anyone
>    on this list, but something like something.apache.org, or from your
>    distro's package manager), you should consider yourself compromised.
> 
> 2. If you build your own mod_jk, you know it will work with your exact
>    environment. No weird problems with slight version mismatches between
>    httpd version or other libraries. No questions about which
>    architecture's files you need to download, etc.
> 
> 3. Building mod_jk from source is relatively trivial. See above. Most
>    Linux distros some with a C compiler by default, and all of them
>    can trivially install gcc.
> 
> Consider trying it.
> 
> Recently, the Tomcat team decided to stop providing binaries for *NIX
> platforms because of the above (maybe that was just for tcnative, but I
> wouldn't be surprised if the policy is now to avoid rolling binaries for
> any non-Java components).
> 
> Why? Because if we wanted to provide binaries for, say, mod_jk, we need
> to support (at least) two architectures: x86 and x86_64. Also, there are
> 4 major versions of Apache httpd: 1.3, 2.0, 2.2, and 2.4. Sometimes,
> even httpd patch level can affect compatibility (though it really
> shouldn't) or maybe it was built against 2.2.11 but the user has 2.2.13
> and wants to know "why no binary?".
> 
> We cannot possibly provide enough binaries to make everyone happy. Since
> it's so easy to build mod_jk, we ask users in *NIX environments to just
> do it.
> 
> We do provide binaries for both 32- and 64-bit Microsoft Windows
> environments for Apache httpd, Microsoft IIS and (wtf?) Netscape,
> because those folks rarely have compilers handy.
> 
> If you have any trouble building mod_jk, please don't hesitate to come
> back for help.
> 
> - -chris


If all the tools are available on the production system (compiler, libraries), then you do
this as a normal user:

myuser$ tar -xvzf tomcat-connectors-1.2.32-src.tar.gz
myuser$ cd tomcat-connectors-1.2.32-src/native/
myuser$ which apxs  
myuser$ ./configure --with-apxs=/usr/sbin/apxs --enable-api-compatibility 
myuser$ make 


(where myuser$ is whatever prompt you have for your user id).

Then you tell the system admin where the location is (probably now in /home/myuser/tomcat-connectors-1.2.32-src/native/),
and have him do as root:

# cd /home/myuser/tomcat-connectors-1.2.32-src/native/
# make install

That should get the mod_jk.so installed. The administrator will then have to configure it
(see tomcat-connectors-1.2.32-src/conf for examples), and finally restart the Apache HTPPD
server.

Hopefully the administrator should be able to do that.

. . . . just my two cents
/mde/


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Mime
View raw message