Detailed Information
Product Name: ServletExec/AS 5.0 for UNIX
Hotfix Name: ServletExec_AS_50_Unix_Hotfix_Oct_2004
Created: 2004-10-11
File Size: 1.00 MB
File URL:
Description: v5.0.0.07
Release Notes
ReleaseNotes.txt for the ServletExec AS for Unix October 2004 hotfix.
ServletExec v5.0.0.07

This hotfix contains only those components that are relevant for SE AS on Unix.
The JAR was updated to fix some bugs.
The native components were updated simply to reflect the current version
[v5.0.0.07] (to avoid confusion).
Hotfixes are cummulative, so they contain all the fixes found in their
previous counterparts.

ServletExec50.jar fixes the following bugs:

- bug #0193: HttpServletRequest.getRemoteUser() returns null when NTLM/IWA Authentication is used
- bug #1391: Custom classloader is not as optimized as it could be 
- bug #1430: Character encoding not being honored for the body of a custom tag
- bug #1438: Webserver default pages not found if default-app deployed without welcome files
             [introduced by the fix for bug #1075 in p03]
- bug #1440: No error occurs if a non DataSource class is configured as a DataSource
- bug #1441: Datasource disappears from Admin UI if datasources.xml uses empty body tags
- bug #1442: Datasource properties disappear from admin UI if an invalid value is specified in datasources.xml  

How to apply any SE hotfix
Generally this involves:

1. Stopping SE and the webserver
2. Renaming the component to be hotfixed
3. Putting the hotfixed component in place of the un-hotfixed component
   (giving it the original name of the un-hotfixed component)

The specifics of doing this can vary based on which component you are patching.
Consult the ServletExec 5.0 Installation Guide to learn which components were
installed with your configuration of ServletExec and where those components
reside, so that you will be able to hotfix them if hotfixed versions were
provided in this hotfix.

- ServletExecXX.jar can typically be found in the
 <ServletExec Install Directory>/lib/ directory.
- Locations for native components (.so's) will vary with webserver brand.

How to apply a ServletExec_Adapter.dll or .so hotfix to an existing
SE 5.0 installation
1. Stop the web server (IIS, SunONE, or Apache).
   NOTE: With IIS this involves stopping the IIS Admin Service
         from the Services Control Panel.
2. Stop ServletExec.
3. Locate the existing adapter that your webserver is currently
   The location and name of your existing/unhotfixed SE adapter depends upon
   which webserver you are using.
   First look in the appropriate chapter of the SE 5.0 Installation Guide
   under the "What was installed" section to learn the default location for
   your adapter.
   If using iWS/SunONE or Apache, then you may also learn this infomation by
   looking in your webserver's config file (magnus.conf, obj.conf, or
   Once you have located it, rename it to something else.

4. If your hotfixed adapter (from the SE hotfix ZIP file) has been provided in
   prebuilt form (.dll, or .so) then place it where the original/unhotfixed
   adapter resides, making sure to rename it accordingly.

   Here are some examples:
    a. If using SE 5.0 AS on Windows with Apache 2.x as your webserver, you could
       look in your httpd.conf to learn the location of the unhotfixed SE Adapter DLL
       file that's currently in use (typically this would be at:
       Then you would rename it to something else such as ApacheModuleServletExec.dll.orig
       and then put ApacheModuleServletExec.dll.APACHE2.x (from the hotfix ZIP) in its
       place, renaming it to remove the ending ".APACHE2.x" portion of its name.

    b. If using iWS 4.x then look in obj.conf.
    c. If using iWS 6.x or SunONE, look in magnus.conf.

    d. If using SE 5.0 AS on Windows with IIS, the default location is:

5.  If you are using Apache on Unix then your hotfixed adapter (from the SE
    hotfix ZIP file) is delivered in source file form (.c file) and you will
    need to build it yourself.
    Here is how:

    a. Copy the appropriate hotfixed adapter source file into an empty folder.
       If using Apache 1.3.x on Unix... the file is mod_servletexec.c
       If using Apache 2.x on Unix...   the file is mod_servletexec2.c

    b. If the adapter you need is mod_servletexec2.c, then once you have it
       copied to an empty folder, rename it to mod_servletexec.c
       (i.e. remove the '2' from it's name)

    c. Build the adapter.
       The exact command used to build the adapter for Apache on Unix may differ
       depending upon the Apache version and the platform (Solaris, Linux, HP-UX, AIX, etc...).
       Because of this, you should examine the /tmp/SEinstall.log file to locate the exact
       command that was used to build the original/unhotfixed version.
       The command involves the use of apxs. For example with Apache 1 on Solaris, the command
       looks something like this:

          <apache install dir>/bin/apxs -i -a -c -n servletexec mod_servletexec.c

          And with Apache 2 on Linux, the command looks something like this:

          <apache install dir>/bin/apxs -n servletexec -i -a -c -D XP_UNIX mod_servletexec.c

          Note that if you are using a less common Unix variant such as HP-UX,
          you'll need to invoke apxs a bit differently.
          As an example, here is how the SE 5.0 installer invokes apxs for
          Apache 2 on our HP-UX 11.11 box and it works fine:

          <apache install dir>/bin/apxs -n servletexec -i -a -c -D XP_UNIX -D APR_WANT_BYTEFUNC mod_servletexec.c

       Locate your platform's 1-line command in your SEinstall.log file, and issue it
       against the hotfixed version manually from the command line.

Whether using Apache 1 or Apache 2, the final name of the module should be
       "", and you should see that file appear where the
       original/unhotfixed version resides to confirm that you truly have the
       newly built, hotfixed version in place.