FAQ

[Tomcat-users] Binary of mod_jk.so for Apache 2.2.x

Leffingwell, Jonathan R CTR FRCSE, JAX 7.2.2
Jul 12, 2011 at 4:57 pm
I don't know the first thing about compiling on Linux. I just want to drop a compiled mod_jk.so into the modules directory. Where can I find the binary, not the source? Thanks!
reply

Search Discussions

20 responses

  • André Warnier at Jul 12, 2011 at 6:12 pm

    Leffingwell, Jonathan R CTR FRCSE, JAX 7.2.2 wrote:
    I don't know the first thing about compiling on Linux. I just want to drop a compiled mod_jk.so into the modules directory. Where can I find the binary, not the source? Thanks!
    What "kind" of Linux ?

    explanation: most Linux "distributions" (RedHat, Suse, Debian, Ubuntu,..) have what is
    called a "software package manager" utility, which is a special tool to install software
    on the system. It will usually get the desired binary modules, already compiled and
    configured, from some repository (often on the web), and install it for you.
    It is the easiest and quickest way of installing software on Linux systems.

    For example, if your system is a Debian or Ubuntu Linux, the following command would
    download and install mod_jk :

    apt-get install libapache2-mod-jk


    ---------------------------------------------------------------------
    To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
    For additional commands, e-mail: users-help@tomcat.apache.org
  • Leffingwell, Jonathan R CTR FRCSE, JAX 7.2.2 at Jul 12, 2011 at 7:05 pm
    Thanks for the reply, André.

    It is Red Hat Linux.


    -----Original Message-----
    From: André Warnier
    Sent: Tuesday, July 12, 2011 2:12 PM
    To: Tomcat Users List
    Subject: Re: Binary of mod_jk.so for Apache 2.2.x

    Leffingwell, Jonathan R CTR FRCSE, JAX 7.2.2 wrote:
    I don't know the first thing about compiling on Linux. I just want to drop a compiled mod_jk.so into the modules directory. Where can I find the binary, not the source? Thanks!
    What "kind" of Linux ?

    explanation: most Linux "distributions" (RedHat, Suse, Debian, Ubuntu,..) have what is
    called a "software package manager" utility, which is a special tool to install software
    on the system. It will usually get the desired binary modules, already compiled and
    configured, from some repository (often on the web), and install it for you.
    It is the easiest and quickest way of installing software on Linux systems.

    For example, if your system is a Debian or Ubuntu Linux, the following command would
    download and install mod_jk :

    apt-get install libapache2-mod-jk


    ---------------------------------------------------------------------
    To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
    For additional commands, e-mail: users-help@tomcat.apache.org
  • Leon Kolchinsky at Jul 12, 2011 at 11:43 pm
    For God's sake,

    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

    Cheers,
    Leon Kolchinsky



    On Wed, Jul 13, 2011 at 05:03, Leffingwell, Jonathan R CTR FRCSE, JAX 7.2.2
    wrote:
    Thanks for the reply, André.

    It is Red Hat Linux.


    -----Original Message-----
    From: André Warnier
    Sent: Tuesday, July 12, 2011 2:12 PM
    To: Tomcat Users List
    Subject: Re: Binary of mod_jk.so for Apache 2.2.x

    Leffingwell, Jonathan R CTR FRCSE, JAX 7.2.2 wrote:
    I don't know the first thing about compiling on Linux. I just want to
    drop a compiled mod_jk.so into the modules directory. Where can I find the
    binary, not the source? Thanks!
    What "kind" of Linux ?

    explanation: most Linux "distributions" (RedHat, Suse, Debian, Ubuntu,..)
    have what is
    called a "software package manager" utility, which is a special tool to
    install software
    on the system. It will usually get the desired binary modules, already
    compiled and
    configured, from some repository (often on the web), and install it for
    you.
    It is the easiest and quickest way of installing software on Linux systems.

    For example, if your system is a Debian or Ubuntu Linux, the following
    command would
    download and install mod_jk :

    apt-get install libapache2-mod-jk


    ---------------------------------------------------------------------
    To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
    For additional commands, e-mail: users-help@tomcat.apache.org
  • Christopher Schultz at Jul 14, 2011 at 4:34 pm
    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
    ---------------------------------------------------------------------
    To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
    For additional commands, e-mail: users-help@tomcat.apache.org
  • Leffingwell, Jonathan R CTR FRCSE, JAX 7.2.2 at Jul 14, 2011 at 5:05 pm
    Thanks, Chris. Unfortunately, I don't have root access, and I know just enough Linux to be dangerous! LOL! The Linux S.A. doesn't know anything about compiling (don't get me started on THAT), so he was asking if there were a binary module to drop into the modules folder. I was hoping to avoid having to learn how to do his job FOR him. :-D

    JL


    -----Original Message-----
    From: Christopher Schultz
    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
    ---------------------------------------------------------------------
    To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
    For additional commands, e-mail: users-help@tomcat.apache.org
  • André Warnier at Jul 14, 2011 at 5:49 pm
    As things happen, I am just in the process of trying to locate a RedHat mod_jk package for
    a client of mine, whose admin also does not seem to find it in RHEL6.
    See the other thread entitled "mod_jk under RedHat ?" for some recent interesting answers.


    ---------------------------------------------------------------------
    To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
    For additional commands, e-mail: users-help@tomcat.apache.org
  • Leffingwell, Jonathan R CTR FRCSE, JAX 7.2.2 at Jul 14, 2011 at 5:56 pm
    André, if you would be so kind as to let me know what you find, I would greatly appreciate it. I will watch the other thread, too. :)


    -----Original Message-----
    From: André Warnier
    Sent: Thursday, July 14, 2011 1:49 PM
    To: Tomcat Users List
    Subject: Re: Binary of mod_jk.so for Apache 2.2.x

    As things happen, I am just in the process of trying to locate a RedHat mod_jk package for
    a client of mine, whose admin also does not seem to find it in RHEL6.
    See the other thread entitled "mod_jk under RedHat ?" for some recent interesting answers.


    ---------------------------------------------------------------------
    To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
    For additional commands, e-mail: users-help@tomcat.apache.org
  • André Warnier at Jul 14, 2011 at 6:01 pm

    Leffingwell, Jonathan R CTR FRCSE, JAX 7.2.2 wrote:
    André, if you would be so kind as to let me know what you find, I would greatly appreciate it. I will watch the other thread, too. :)
    Well, according to the one and the same Mark Eggers who also provided your last response,
    the answer seems to be a package named "mod_jk-ap20-1.2.31-1.ep5.el4.x86_64.rpm" or similar.
    But it may not be located in the main RHEL6 software repository.

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
    For additional commands, e-mail: users-help@tomcat.apache.org
  • André Warnier at Jul 14, 2011 at 6:10 pm

    André Warnier wrote:
    Leffingwell, Jonathan R CTR FRCSE, JAX 7.2.2 wrote:
    André, if you would be so kind as to let me know what you find, I
    would greatly appreciate it. I will watch the other thread, too. :)
    Well, according to the one and the same Mark Eggers who also provided
    your last response, the answer seems to be a package named
    "mod_jk-ap20-1.2.31-1.ep5.el4.x86_64.rpm" or similar.
    But it may not be located in the main RHEL6 software repository.
    Addendum :
    If you can wait until next Tuesday night 19/7, I will certainly know by then.
    On that day, I have to go on-site precisely to install Apache/mod_jk/Tomcat onto a RHEL6
    new system, and I will have access to all RHEL6 repositories, with a competent sysadmin to
    help me (he just does not know mod_jk).
    So if it can be found, we will.

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
    For additional commands, e-mail: users-help@tomcat.apache.org
  • Leon Kolchinsky at Jul 15, 2011 at 12:25 am
    Hi,

    Hmm, I didn't know that you're not managing this box ;)
    I'm actually a Linux SysAdmin and not a big specialist in mod_jk ;)
    What version of RedHat it is?
    What application do you want to run on Tomcat behind Apache Httpd?

    If you want I could help your SysAdmin with compilation and basic
    configuration.

    Cheers,
    Leon Kolchinsky



    On Fri, Jul 15, 2011 at 03:03, Leffingwell, Jonathan R CTR FRCSE, JAX 7.2.2
    wrote:
    Thanks, Chris. Unfortunately, I don't have root access, and I know just
    enough Linux to be dangerous! LOL! The Linux S.A. doesn't know anything
    about compiling (don't get me started on THAT), so he was asking if there
    were a binary module to drop into the modules folder. I was hoping to avoid
    having to learn how to do his job FOR him. :-D

    JL


    -----Original Message-----
    From: Christopher Schultz
    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
    -----BEGIN PGP SIGNATURE-----
    Version: GnuPG v1.4.10 (MingW32)
    Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

    iEYEARECAAYFAk4fGnQACgkQ9CaO5/Lv0PCRlgCfd41tx9q8BpKfY35elKUCmokO
    b9oAoIC3QamvoAhLvtageSz0/zQzEVxE
    =0myN
    -----END PGP SIGNATURE-----

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
    For additional commands, e-mail: users-help@tomcat.apache.org
  • André Warnier at Jul 15, 2011 at 7:37 am
    For both threads :
    Binary of mod_jk.so for Apache 2.2.x
    and
    mod_jk under RedHat ?

    Here is apparently the deal with mod_jk and Redhat (quoted from my competent sysadmin) :

    In the RedHat product "Red Hat Enterprise Linux Server" (RHELS), there is no repository
    containing a pre-packaged mod_jk module.

    To obtain such a package, the client has to purchase the separate RedHat package "JBoss
    Enterprise Web Server", which contains mod_jk.

    He adds (and I do not understand what that means, but someone else might):

    '"JBoss Enterprise Web Server" is not a "Channel" that can be added to RHELS.'

    I may comment on this later on, but for now, it seems that the alternatives for someone
    who for whatever reason wants/needs to stick with RHELS and the pre-packaged software that
    it contains, the alternatives to connect Apache and Tomcat are :
    - use mod_proxy and mod_proxy_ajp
    or
    - use mod_proxy and mod_proxy_http
    (which are part of Apache 2.x, which is available in RHELS)

    or

    purchase the additional RedHat product "JBoss Enterprise Web Server", in which case you
    can also use the included mod_jk package.


    For someone who wants to stick with RHELS, does not want to buy the additional "JBoss
    Enterprise Web Server", but can/is allowed to install other packages, an additional
    possibility is to use mod_jk, after compiling it from source.


    ---------------------------------------------------------------------
    To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
    For additional commands, e-mail: users-help@tomcat.apache.org
  • Leffingwell, Jonathan R CTR FRCSE, JAX 7.2.2 at Jul 14, 2011 at 5:08 pm
    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
    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
    ---------------------------------------------------------------------
    To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
    For additional commands, e-mail: users-help@tomcat.apache.org
  • Mark Eggers at Jul 14, 2011 at 5:22 pm

    ----- 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
    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
  • Leffingwell, Jonathan R CTR FRCSE, JAX 7.2.2 at Jul 15, 2011 at 2:54 pm
    There is no "apxs" on the Linux server. The S.A. confirmed this. That file and nothing closely resembling it are found anywhere on the whole box. Is it needed to compile mod_jk?



    -----Original Message-----
    From: Mark Eggers
    Sent: Thursday, July 14, 2011 1:22 PM
    To: Tomcat Users List
    Subject: Re: Binary of mod_jk.so for Apache 2.2.x
    ----- 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
    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
  • Mark Eggers at Jul 15, 2011 at 5:19 pm

    ----- 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>; Mark Eggers <its_toasted@yahoo.com>
    Cc:
    Sent: Friday, July 15, 2011 7:53 AM
    Subject: RE: Binary of mod_jk.so for Apache 2.2.x

    There is no "apxs" on the Linux server.  The S.A. confirmed this.
    That file and nothing closely resembling it are found anywhere on the whole
    box.  Is it needed to compile mod_jk?
    Yes, and you will need a collection of other include files and libraries that are probably not installed on your system.

    Building mod_jk on a RedHat system is slightly complicated by the fact that RedHat breaks up packages.

    For example, if you install the apr and apr-util packages, you might expect to have all the tools required to build software with Apache's portable runtime libraries.

    You don't. You will need to install apr-devel and apr-util-devel in order to build other software using these libraries. The apr and apr-util packages contain only what is required to run software built with these packages.

    Building mod_jk on RedHat (at least Fedora), requires a collection of development tools and packages. At the top of the requirements chain, these are:

    1. httpd-devel
    This package provides /usr/sbin/apxs among other things.

    2. apr-devel
    The include files for building software with the apache portable runtime libraries.

    3. apr-util-devel
    The include files for the utilities library of the apache portable runtime libraries

    4. Java JDK
    Note, the JRE will NOT work. You should download and install this from Oracle, although there are ways to get this installed using the RedHat package manager. There are include files in $JAVA_HOME/include and $JAVA_HOME/include/linux that you will need.

    If yum is set up properly (at least on Fedora), the dependencies for the first three packages will be pulled in when you request the following (as root):

    yum install httpd-devel apr-devel apr-util-devel

    In part, you should see the following get installed.

    perl (if not installed already - can't imagine why it wouldn't be)
    pkgconfig
    db4-devel (which requires db4 and db4-cxx)
    expat-devel (which requires expat)
    openldap-devel (which requires openldap,cyrus-sasl-devel)

    cyrus-sasl-devel requires a set of packages as well.
    cyrus-sasl
    cyrus-sasl-lib

    Hopefully everything else should be in place on your system.

    Again, in a sane world yum will pull in the required dependencies if you just do the following as root:

    yum install httpd-devel apr-devel apr-util-devel

    Yum will come back with a list of additional packages it needs to install in order to meet the requirements.

    This is how it works on a Fedora system, which is basically the beta testing environment for RedHat EL releases.

    For mod_ssl, you shouldn't have to build it. At least on a Fedora system, mod_ssl is provided by the mod_ssl package.

    Installing that as root with:

    yum install mod_ssl

    will bring in the openssl package. You will need the openssl package and the openssl-devel package in order to build the Tomcat native libraries packaged in $CATALINA_HOME/bin/tomcat-native.tar.gz.

    Hopefully between you and your system admin, you can decipher the above mail message.

    . . . . just my two cents.

    /mde/

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
    For additional commands, e-mail: users-help@tomcat.apache.org
  • Christopher Schultz at Jul 14, 2011 at 6:37 pm
    Jonathan,
    On 7/14/2011 1:08 PM, Leffingwell, Jonathan R CTR FRCSE, JAX 7.2.2 wrote:
    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? Yes.
    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
    The "# which apxs" was intended to be a command to determine the
    location of Apache httpd's "apxs" program, which is a
    configuration-dumping utility to help with building Apache httpd
    modules. apxs if often found in /usr/sbin/apxs so Leon's post was using
    that as an example:
    ./configure --with-apxs=/usr/sbin/apxs --enable-api-compatibility
    Replace /usr/sbin/apxs with whatever the result of "which apxs" is. If
    that doesn't return anything, you may have to have your SA install the
    Apache httpd development package or something. It might also be called
    "apxs2" (that's the case in my Debian Lenny environment).

    Good luck,
    - -chris
    ---------------------------------------------------------------------
    To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
    For additional commands, e-mail: users-help@tomcat.apache.org
  • Mark Eggers at Jul 14, 2011 at 8:22 pm

    ----- Original Message -----

    From: Christopher Schultz <chris@christopherschultz.net>
    To: Tomcat Users List <users@tomcat.apache.org>
    Cc:
    Sent: Thursday, July 14, 2011 11:36 AM
    Subject: Re: Binary of mod_jk.so for Apache 2.2.x

    -----BEGIN PGP SIGNED MESSAGE-----
    Hash: SHA1

    Jonathan,
    On 7/14/2011 1:08 PM, Leffingwell, Jonathan R CTR FRCSE, JAX 7.2.2 wrote:
    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? Yes.
    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
    The "# which apxs" was intended to be a command to determine the
    location of Apache httpd's "apxs" program, which is a
    configuration-dumping utility to help with building Apache httpd
    modules. apxs if often found in /usr/sbin/apxs so Leon's post was using
    that as an example:
    ./configure --with-apxs=/usr/sbin/apxs --enable-api-compatibility
    Replace /usr/sbin/apxs with whatever the result of "which apxs" is. If
    that doesn't return anything, you may have to have your SA install the
    Apache httpd development package or something. It might also be called
    "apxs2" (that's the case in my Debian Lenny environment).

    Good luck,
    - -chris
    An addendum concerning building mod_jk on a RedHat based system:

    RedHat often (always?) splits libraries from their associated include files and development resources. It really doesn't save a lot of space, so I guess the only reason is to create a clean production (read, can't build software here) environment.

    In order to build mod_jk on Fedora (and probably CentOS, RedHat EL), you'll need to have the following installed (plus the normal development tools).

    httpd-devel (provides /usr/sbin/apxs
    apr-devel (provides the appropriate include files)
    apr (required by apr-devel)
    apr-util-devel (required by httpd-devel)
    apr-util (required by apr-util)

    There are other requirements buried in the list above, but if your admin installed these yum should pull in the requirements.

    It's good to have a development system that mirrors the software versions running on the production system, with the addition of all the development libraries and tools.

    . . . . just my two cents.

    /mde/

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
    For additional commands, e-mail: users-help@tomcat.apache.org
  • Leffingwell, Jonathan R CTR FRCSE, JAX 7.2.2 at Jul 15, 2011 at 12:15 pm
    Big thanks to Chris, Andre, and everyone else for all of the guidance! I think I'm going to do this:

    1. Compile Apache 2.2.19 in /myuser/ space (since I don't have root or admin privileges).

    2. Ask the admin to do his part in taking the compiling code and installing it.

    I have a question about doing this with mod_ssl, but I think it would be best for me to start a different thread with this. Thanks again!

    Jonathan


    -----Original Message-----
    From: Christopher Schultz
    Sent: Thursday, July 14, 2011 2:37 PM
    To: Tomcat Users List
    Subject: Re: Binary of mod_jk.so for Apache 2.2.x

    -----BEGIN PGP SIGNED MESSAGE-----
    Hash: SHA1

    Jonathan,
    On 7/14/2011 1:08 PM, Leffingwell, Jonathan R CTR FRCSE, JAX 7.2.2 wrote:
    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? Yes.
    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
    The "# which apxs" was intended to be a command to determine the
    location of Apache httpd's "apxs" program, which is a
    configuration-dumping utility to help with building Apache httpd
    modules. apxs if often found in /usr/sbin/apxs so Leon's post was using
    that as an example:
    ./configure --with-apxs=/usr/sbin/apxs --enable-api-compatibility
    Replace /usr/sbin/apxs with whatever the result of "which apxs" is. If
    that doesn't return anything, you may have to have your SA install the
    Apache httpd development package or something. It might also be called
    "apxs2" (that's the case in my Debian Lenny environment).

    Good luck,
    - -chris
    ---------------------------------------------------------------------
    To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
    For additional commands, e-mail: users-help@tomcat.apache.org
  • Jeff Allison at Jul 15, 2011 at 12:20 pm
    Isn't mod_jk deprecated in favour of mod_ajp.
    On Jul 15, 2011 10:15 PM, "Leffingwell, Jonathan R CTR FRCSE, JAX 7.2.2" wrote:
    Big thanks to Chris, Andre, and everyone else for all of the guidance! I
    think I'm going to do this:
    1. Compile Apache 2.2.19 in /myuser/ space (since I don't have root or
    admin privileges).
    2. Ask the admin to do his part in taking the compiling code and
    installing it.
    I have a question about doing this with mod_ssl, but I think it would be
    best for me to start a different thread with this. Thanks again!
    Jonathan


    -----Original Message-----
    From: Christopher Schultz
    Sent: Thursday, July 14, 2011 2:37 PM
    To: Tomcat Users List
    Subject: Re: Binary of mod_jk.so for Apache 2.2.x

    -----BEGIN PGP SIGNED MESSAGE-----
    Hash: SHA1

    Jonathan,
    On 7/14/2011 1:08 PM, Leffingwell, Jonathan R CTR FRCSE, JAX 7.2.2 wrote:
    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? Yes.
    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
    The "# which apxs" was intended to be a command to determine the
    location of Apache httpd's "apxs" program, which is a
    configuration-dumping utility to help with building Apache httpd
    modules. apxs if often found in /usr/sbin/apxs so Leon's post was using
    that as an example:
    ./configure --with-apxs=/usr/sbin/apxs --enable-api-compatibility
    Replace /usr/sbin/apxs with whatever the result of "which apxs" is. If
    that doesn't return anything, you may have to have your SA install the
    Apache httpd development package or something. It might also be called
    "apxs2" (that's the case in my Debian Lenny environment).

    Good luck,
    - -chris
    -----BEGIN PGP SIGNATURE-----
    Version: GnuPG v1.4.10 (MingW32)
    Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

    iEYEARECAAYFAk4fN0kACgkQ9CaO5/Lv0PD2ZwCfcQuD5WScbq+HJgCKTHZtY3JY
    Ii0AoK8WtgF4SmXAemVGRmMde4f0K8P1
    =HFWz
    -----END PGP SIGNATURE-----

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
    For additional commands, e-mail: users-help@tomcat.apache.org
  • Rainer Jung at Jul 15, 2011 at 1:49 pm

    On 15.07.2011 14:20, Jeff Allison wrote:
    Isn't mod_jk deprecated in favour of mod_ajp.
    No

    Rainer

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

Related Discussions