Application Server Solutions for Microsoft IIS and ASP.NET
       solutions   products   partners   company   support   downloads         store
ServletExec Self-Help: FAQ
Back to Search >  Back to Search Results

Faq ID 14
Product ServletExec
Category Installation
Question I've installed ServletExec/AS with Apache on UNIX but it doesn't work. What can I do to verify my installation?
  1. Verify that a valid JDK or JRE is installed on your machine.

  2. Verify the JAVA_HOME environment variable is not set. If it is set then verify it is correctly set to the installation directory of the JDK or JRE you are using.

  3. Verify that Apache 1.3.x or 2.0.x (or 2.2.x if using SE 6.0 or higher) is installed.
    And make sure that it is a supported Apache distribution as described in FAQ #141
    Also make sure that your Apache was built with DSO support enabled.

    The method to use to determine if DSO is installed in an Apache build is to run the command:
    <apache-executable> -l
    where <apache-executable> may be "Apache.exe" on Windows or "httpd" on some UNIX, etc. If the result of this command shows something like the following ("mod_so.c" is required):

    Compiled in modules:

    ... then DSO is installed in the Apache build.

  4. Verify that you are using a supported C-compiler.
    Here's a quote from section 6.2.1 of the SE 5.0 Installation Guide (System Requirements section):
    In addition to a JDK 1.3-, or 1.4-compliant VM, these installations require an ANSI C compiler (GNU version 2.8.1 or higher preferred. Vendor-specific C compilers are not supported) and a system-specific dynamic shared object loader.

    Your apxs should contain:
    my $CFG_CC = q(gcc);
    my $CFG_CC = q(cc);
    If you don't have GCC installed then get GCC installed, and then execute the steps for rebuilding your APXS (given below in this FAQ)
  5. If the ServletExec installer failed to compile the mod_servletexec.c file then verify the compiler and link-editor specified by $CFG_CC and $CFG_LD_SHLIB in your apxs script are in your PATH. If they are then verify your apxs script doesn't begin with:


    If it does then you need to install PERL on your system and you need to rebuild apxs as described below. If it doesn't then make sure it doesn't look as follows:

    my $CFG_CFLAGS_SHLIB = ''; # substituted via Makefile.tmpl
    my $CFG_LD_SHLIB = ''; # substituted via Makefile.tmpl
    my $CFG_LDFLAGS_SHLIB = ''; # substituted via Makefile.tmpl

    If it does then your apxs script needs to be updated. This occurs (often) when Apache is initially configured without shared module support (the default configuration) and then re-configured and rebuilt with shared module support. Since the makefile that creates apxs from depends only on the sources, apxs will not be updated when you re-configure. You should remove apxs from your source tree, remake and reinstall to get a fully configured/operational apxs. Note: you cannot remake and then copy the apxs--it is modified further in the configuration process.

    To rebuild apxs from the source execute the following commands:

    cd <apache-src-dir>
    rm src/support/apxs
    make install

    If your apxs script is correct and you are using the Sun compiler then the problem is mod_servletexec.c contains C++ style comments. To fix this edit your apxs script and add the -xCC option to the definition of $CFG_CFLAGS so that the Sun compiler will accept C++ style comments. Re-install ServletExec after making this change.
    See Section of the SE 5.0 Installation Guide for more details

  6. Stop the ServletExec application by invoking the StopServletExec script and stop the web server if they are running.

  7. Verify the httpd.conf file has been updated as described in Chapter 6 of the Installation Guide.

  8. Restart the web server.

  9. Restart the ServletExec application by invoking the StartServletExec script. If error messages appear in the console or in ServletExec.log then send them to Note that you should at least see some ServletExec initialization messages.

  10. Try the following URLs:


    If these don't work then look for error messages in the ServletExec.log file and send them to

company media information terms of use privacy policy contact us