Release Notes for iPlanetTMApplication Server, Enterprise Edition

Version 6.5

Updated May 10, 2002

These release notes contain important information available at the time of the Version 6.5 release of iPlanetTM Application Server, Enterprise Edition. New features and enhancements, installation notes, known problems, and other late-breaking issues are addressed here. Read this document before you begin using iPlanet Application Server, Enterprise Edition.

These release notes contain the following sections:

What's New in iPlanet Application Server, Enterprise Edition 6.5

Note The following list is based on new features in iPlanet Application Server, Enterprise Edition, 6.5 release. For the complete list of changes from iPlanet Application Server 6.0, SP1, refer to the Release Notes for each intervening Support Pack releases at: http://docs.iplanet.com/docs/manuals/ias.html.
    iPlanet Application Server, Enterprise Edition, 6.5 includes enhancements described in the following sections:

    JDK 1.3.1 Support

    IBM JDK 1.3.1 is bundled with iPlanet Application Server, Enterprise Edition, 6.5.

    CTS Compliance

    iPlanet Application Server, Enterprise Edition, 6.5 complies with the latest CTS 1.2.1.d specifications.

    Performance Improvements

    iPlanet Application Server, Enterprise Edition, 6.5 sports the following performance improvements compared to 6.0, SP4:

    Database Infrastructure Enhancements

    Encina has been replaced with the Java TM Transaction Service Reference Implementation (JTS RI), with suitable modifications for production environments. The following enhancements have been made to the database support infrastructure: These new features affect various processes and functions of iPlanet Application Server, as described below:

    Driver Registration

    DataSource Registration

    Connection Pooling

    The following enhancements have been made to the connection pooling infrastructure:

    Transaction Service

    The following enhancements have been made to the Transaction Service:

    Support for Message Driven Beans

    Message-driven beans are now supported by iPlanet Application Server. The Administration Tool and Deployment Tool offers added functionality to administer and deploy message-driven beans.

    The message-driven bean functionality in this release is certified for developer use only.

    For more information, see chapter 7, "Using Message Driven Beans" in the Developers Guide, and chapter 15, "Configuring JMS Providers", in the Administration Guide.


    Note iPlanet Message Queue for Java 2.0 is not supported on AIX. You can use a third party Java messaging middleware that is supported on AIX. Ensure that the message queue you plan to use, conforms to Chapter eight, "JMS Application Server Facilities", of the JMS specification.

    For information on configuring a third party JMQ, see Chapter 11, "Administering Message Driven Beans", in iPlanet Application Server Administrator's Guide.

      ORB Upgrade

      The ORB bundled with iPlanet Application Server has been replaced by J2EE 1.3 RI ORB.

      The J2EE 1.3 RI ORB is Portable Object Adaptor (POA) compliant and makes upgrades easier in the future.

      This ORB upgrade provides better performance and scalability in the rich client path. A few bugs in the J2EE 1.3 RI ORB have been fixed in the ORB version bundled with iPlanet Application Server.

      A few classes, which were earlier part of J2EE 1.2 RI ORB, have been moved to JDK1.3. These are packaged into J2EERIORB. The orb.properties file has been changed to replace IBMORN with J2EERIORB.

      SOAP Enhancements

      The latest version of SOAP (SOAP 2.2) is available on the iPlanet Application Server product CD. To make SOAP applications run on iPlanet Application Server, the following two modifications are needed:

      Developer Resources

      iPlanet Application Server now includes a Developer Resources component to assist developers developing applications using the Forte for Java IDE, and seamlessly deploying those applications to the iPlanet Application Server and Web Server.

      Developer's Resources for iPlanet Application Server 6.5 includes:

      For more information about installing and using the Developer Resources Integration modules for developing applications for the iPlanet Application Server, consult the ReadMe located on the product CD in devtools/readme.html.

      Additionally, the most up-to-date Developers Resources documentation can be found at: http://docs.iplanet.com. Select the Developer Pack link to locate the latest documentation for developers.

      Installation, Administration, and Deployment Enhancements

      This section describes the following topics:

      Installation Changes

      The following changes have been made to iPlanet Application Server installation procedure: Deployment Tool Enhancements

      Administration Tool Enhancements

      The 6.5 administration framework provides improved administration control, monitoring, and tracing capabilities.

      The following monitoring and tracing features are available in 6.5:

      Sample Application Enhancements

      The following samples have been added in iPlanet Application Server, Enterprise Edition 6.5 release: The sources and documentation for the sample applications are available at: developer.iplanet.com

      Product Packaging

      iPlanet Application Server, Enterprise Edition 6.5, CD includes the following products and documentation:

      Compatibility with Previous Releases

      This section describes changes made in 6.5 that affect applications developed or deployed on earlier versions of iPlanet Application Server, Enterprise Edition.

      Native Drivers Deprecated

      Admin Command Line Tool Removed

      JSP Caching Changes

      Compiler Changes

      iPlanet Application Server, Enterprise Edition, 6.5 sources have been recompiled using IBM Visual Age C++ Professional for AIX 5.0.

      As a result, Applogics based C++ applications might have to be recompiled and change native code to follow ANSI/ISO C++ standard, and install additional OS/Compiler patches.

      You will have to rename all occurrences of gx_session_id to GX_SESSIONID, if you are using this parameter in your applications.

      Internationalization Changes

      JSP Includes

      To work around multi-byte character issues, use the following two methods to include JSPs:

      Message Driven Beans

      iPlanet Application Server 6.5 supports GX.SetCharset() method of deprecated Netscape Application Server API. This method is extensively used to support Multibyte locale functionality in iPlanet Application Server.

      Use this method to display Japanese messages correctly in a message-driven bean Java Client.

      Since the application uses com.kivasoft.util.GX, as it is an internal API, you have to set $LIBPATH to /ias/gxlib to enable the JMS client to send messages.

      Memory Settings

      The default JVM arguments on iPlanet Application Server, Enterprise Edition, 6.5 are as follows:

      JAVA_ARGS="-Xbootclasspath/a:$JAVA_HOME/jre/lib/ext/j2eeorb.jar -Xmine16m -Xoss1536k -Xss1m -Xms256m -Xmx512m -Xgcpolicy:optavgpause"

      The heap values will need to be changed based on available system memory. In previous versions of iPlanet Application Server, the default values of minimum & maximum heap used to be 64 MB. Due to the change in default values (256 MB minimum, 512 MB maximum),the memory startup footprint will be higher.


      Note If your system does not have 1GB memory, then reduce the maximum heap size to fit your system's resources.

      Applogics Deprecated

      The Applogics framework is deprecated with this release of iPlanet Application Server and will not be supported in future releases.

      Software and Hardware Requirements

      Your AIX system must meet the following requirements before you can install iPlanet Application Server.

      Installation Notes

      This section contains late-breaking information about installing iPlanet Application Server, Enterprise Edition, 6.5. For detailed information about installation procedures, see iPlanet Application Server Installation Guide.

      Information Specific to AIX

      • The ulimit values for data and memory should be set to unlimited.

      • If the installation path of iPlanet Application Server is too long, you will get the following error message in the kjs log:

        while starting kjs:LoadJavaVM: unable to open DLL (/usr/java131/jre/bin/classic/libjvm.a)
        LIBPATH too long
        File name too long


      Note Documentation shipped with iPlanet Application Server, Enterprise Edition, 6.5 does not contain AIX specific instructions. Use the Solaris® specific instructions for your AIX installation of iPlanet Application Server.

      Ensure to read the "Prerequisites for Installation" in Chapter 2, "Preparing to Install", in iPlanet Application Server Installation Guide.

        Installing iPlanet Directory Server 5.0 SP1 Patch

        This patch should be installed if you are planning to use a fresh installation of iPlanet Application Server, Enterprise Edition 6.5 with a remote user directory. This patch must be installed even if you are using iPlanet Directory Server 4.13 or later versions, as your user directory.

        For detailed instructions on installing the iPlanet Directory Server 5.0 SP1 patch, follow the directions listed for Solaris in iPlanet Application Server Installation Guide.

        Certified Directory Servers


        The following directory servers are certified to work with iPlanet Application Server 6.5.
        Table 5 Certified Directory Servers
        Directory Server Version
        iPlanet Directory Server 5.1

        5.0 SP1 (bundled with iPlanet Application Server 6.5)

        4.13

        Certified Web Servers

        The following Web servers are certified to work with iPlanet Application Server, Enterprise Edition 6.5.
        Table 6 Certified Web Servers
        Web Server

        Interface
        iPlanet Web Server, Enterprise Edition 6.0, SP1, SP2, or 6.0.1 NSAPI
        iPlanet Web Server Enterprise Edition 4.1, SP7 or later NSAPI
        Microsoft Internet Information Server 4.0 (Windows NT) ISAPI
        Microsoft Internet Information Server 5.0 (Windows 2000) ISAPI
        Apache 1.3.19 APACHEAPI

        Certified JVMs

        The following JVMs are certified to work with iPlanet Application Server 6.5.
        Table 7 Certified JVMs

        Platform

        Version

        JVM
        AIX IBM AIX 4.3.3.0.09 JDK 1.3.1ca1311-20011123a

        Certified Third Party JDBC Database Drivers

        The following Third Party JDBC drivers are certified to work with iPlanet Application Server 6.5.
        Table 8 Third party JDBC database drivers certified in 6.5 for AIX 4.3.3

        Database Vendor

        JDBC Driver
        Oracle Oracle 8.1.7 (Type 4 and Type 2), 9i
        Merant SequeLink DataDirect Java 5.1 (all databases supported by DDJ5.1)
        Sybase jConnect for JDBC 5.2 Type 4
        IBM DB2 IBM DB2 7.1 JDBC Client
        Informix Informix JDBC v2.2 Type 4

        Certified Native Type 2 Database Servers and Clients

        iPlanet Application Server 6.5 continues to support the database clients and servers for the iPlanet Application Server Type 2 JDBC Database Drivers listed here.
        Table 9 Certified Native Type 2 database servers and clients for 6.5

        Database Server

        Database Client
        Oracle 7.3.4, 8.0.x, 8i, 9i Oracle8i 8.1.7
        Sybase 12 Sybase Open/Client System 12
        DB2 7.1 DB2 6.1, 7.1
        Informix 9.2 Informix SDK 2.40
        Microsoft SQL Server 7, 2000 ODBC 3.51

        Note On Oracle, transactions are supported on Oracle 8.1.7 or later server versions.

        Documentation Updates

        The following manuals and online help tools were updated for iPlanet Application Server, Enterprise Edition 6.5.

        Note Documentation shipped with iPlanet Application Server, Enterprise Edition, 6.5 does not contain AIX specific instructions. Use the Solaris specific instructions for your AIX installation and administration of iPlanet Application Server.

          Installation Guide

          The iPlanet Application Server, Enterprise Edition 6.5 release includes the following changes for the Installation Guide:
          • New database registration procedures.
          • Updated Preinstall requirements.

          Administrator's Guide

          The iPlanet Application Server, Enterprise Edition 6.5 release includes the following changes for the Administrator's Guide:
          • New database driver registration procedures.
          • New datasource registration procedures.
          • New transaction manager configuration and managing information.
          • New chapter added on message-driven beans and JMS configuration.
          • Updated LDAP failover configuration procedures for iDS 5.0.
          • Major bug fixes.

          Migration Guide

          The iPlanet Application Server, Enterprise Edition 6.5 release includes the following changes for the Migration Guide:
          • Added new chapter on migrating applications to iPlanet Application Server 6.5.

          Developer's Guide

          The iPlanet Application Server, Enterprise Edition 6.5 release includes the following changes for the Developer's Guide:
          • Added new chapter on deploying message-driven beans.
          • Updated old deployment descriptor XML file samples with new samples for 6.5.
          • Major bug fixes.

          Deployment Tool Online Help

          The iPlanet Application Server, Enterprise Edition 6.5 release includes the following changes for the Deployment Tool Online Help:
          • Updated datasource registration procedures.
          • Added message-driven bean specific information.
          • Updated all information and procedures to reflect changes made in 6.5
          • Major bug fixes

          Performance and Tuning Guide

          The iPlanet Application Server, Enterprise Edition 6.5 release includes the following changes for the Performance and Tuning Guide:
          • Updated to include tuning parameters for JDK 1.3.1, and the new transaction manager.
          • Improved navigation of contents.

          Registry Guide

          The iPlanet Application Server, Enterprise Edition 6.5 release includes the following changes for the Registry Guide:
          • Updated with new registry keys for datasource, transaction manager, and message-driven beans.

          Known Problems and Limitations

          This section describes known problems and associated workarounds with iPlanet Application Server, Enterprise Edition 6.5. This information is organized into the following sections:

          Installation Issues

          This section describes the known iPlanet Application Server, Enterprise Edition 6.5 installation issues, and the associated workarounds.
          < <

          ID Summary
          524125
          Problem
          In custom installation mode, at the point where the user is asked if he wants to populate the Directory Server with entries, if 'None' is chosen then no entry is created.

          After installation, connecting to the server fails since the user is not in the LDAP information.

          Workaround
          Instead of choosing 'None', the user should select the default option: 'Suggest'.
          -
          Problem
          Creation of administrator user entry in the remote user directory fails if that directory is read-only.
          The administrator user entry must exist in the user LDAP directory for registering the server through iPlanet Application Server Administration Tool (iASAT).

          Workaround
          To enable iPlanet Application Server to authenticate against a remote user directory server, complete the installation and then perform the following steps:

          1. Create an adminuser.ldif file with the following entries:


            		2.
            dn: uid=iasadmin., ou=People, o=iplanet.com
            changetype: add
            cn: Nas Administrator
            sn: Nas Administrator
            givenname: iAS admin
            objectclass: top
            objectclass: person
            objectclass: inetorgperson
            ou: People
            uid: iasadmin
            userpassword: password

          2. Run the ladapmodify command:

            3. < iAS_InstallDir /shared/bin> ldapmodify -D "cn=Directory Manager" -p < ldap_PortNo. > -w < password > -a -f adminuser.ldif.
          4632617
          Problem
          iPlanet Console hangs if iPlanet Application Server is installed in the same directory where iPlanet Directory Server 4.13 is installed.
          This problem occurs because the JDK version used by iPlanet Application Server and iPlanet Directory Server 4.13 are different.

          Workaround
          Install iPlanet Application Server in a different directory from the one in which iDS 4.13 is installed.

          Core Server Issues

          This section describes the known iPlanet Application Server, Enterprise Edition 6.5 core server issues, and the associated workarounds.

          ID Summary
          4626356
          Problem
          Administration Tool fails to connect to application server after the primary fails.
          This would happen if you have a cluster set-up configured with Maxbackups=0.

          If Maxbackups is specified as 0 (none), then there is no backup application server and the alternates change to the standalone state. However, when the primary comes up again, it cannot connect to the alternate as it's in standalone mode.

          Workaround
          When configuring a cluster, ensure that Maxbackups is 1 or more, not 0.
          4639210
          Problem
          Transaction propagation does not work consistently.
          If two KJS' are participating in a transaction and only one of them is made recoverable, then this configuration cannot lead to proper recovery.

          Workaround
          Ensure that in a recoverable scenario, all participant KJS' should be recoverable. Either all should be recoverable or none should be recoverable.
          4633284
          Problem
          When using DB2 as the database, transactions are not rolled back even though one of the application servers fails to recover from a crash.
          This problem occurs due to limitations in DB2.

          Workaround
          If your iPlanet Application Server installation is using DB2 as the database, then ensure that both iPlanet Application Server and DB2 are installed on the same server.
          4633274
          Problem
          KJS crashes during transaction recovery, if DB2 is in an inconsistent sate.
          If recovery is done when DB2 is in an inconsistent state, the recovery call to DB2 dumps core and crashes KJS.

          Workaround
          Disable recovery in iPlanet registry to bring up KJS again.
          542273
          Problem
          The CORBA Executive Server crashes when exceptions are thrown.
          536256
          Problem
          A JSP of size larger than 185 KB cannot be executed on iPlanet Application Server.
          560053
          Problem
          Struts applications fail when the Versioning key is enabled.

          Workaround
          Do not enable dynamic reloading. Ensure that the Versioning key is set to 1 in the registry.

          To disable dynamic reloading:

          1. Start iPlanet Registry Editor, kregedit, and modify the Disable value under the Versioning key: SOFTWARE/iPlanet/Application Server/6.0/CCS0/SYSTEM_JAVA/Versioning
          2. Set the Disable value to 1
          3. Restart iPlanet Application Server to enable the change.
          557991
          Problem
          The security principal class is not invoked automatically when security is enabled for RMI/IIOP based applications.

          Workaround
          Before running RMI/IIOP based applications, the org.omg.CORBA.ORBClass property value should be changed to com.netscape.ejb.client.ClientORB in the orb.properties file under iASInstDir /ias/usr/java/jre/lib.

          For example, org.omg.CORBA.ORBClass=com.netscape.ejb.client.ClientORB.
          -
          Problem
          For distributed sessions, a negative value for setMaxInactiveInterval() will make the session timeout immediately.

          Workaround
          Pass a very high value as an argument to setMaxInactiveInterval().
          4640812, 4640854, 4643711
          Problem
          Memory growth when using iPM and BillerXpert with iPlanet Application Server 6.5.

          Workaround
          Disable the explicit Garbage Cleaner by uncommenting JAVA_GX_ARGS=-DGX.cleaner.enabled key in iAS_InstallDir/ias/env/iasenv.ksh file on AIX.

          On AIX, the JAVA_GX_ARGS=-DGX.cleaner.enabled entry is by default set to no .

          Deployment Tool Issues

          This section describes the known iPlanet Application Server, Enterprise Edition 6.5 Deployment Tool issues, and the associated workarounds.

          ID Summary
          548426
          Problem
          Redeployment of an updated version of an application does not remove the contents of the previous deployment from the file system area of the application area. The default location of deployed files is install_dir/ias/APPS/modules/module_name/ or APPS/ear_name/module_name/ .

          In addition to leftover file system content, some of the application server registry settings are also not overwritten and/or removed as an application is redeployed.

          This behavior can lead to older application settings remaining in effect after a redeploy.

          Workaround
          To perform a clean redeployment, first perform a remove followed by a deploy.
          537084 Problem
          If iPlanet Application Server is installed as root on a machine using the custom installation, the Deployment Tool (iASDT) is not accessible by other uses to create applications on Unix platforms.

          Workaround
          If a user "A" has installed app server and ALL its components, then any other user "B" needs following permissions in order to run the Deploy Tool properly (note that iasdir refers to the installation location of iPlanet Application Server):

          1. iASDT reads/writes in iasdir/registry/reg.dat. Make sure that the directory iasdir/ias/registry has ALL permissions for user "B".
          2. Deploy Tool writes its temporary xml files from descriptors, EJB skels and stubs into, iasdir/ias/tmp. Make sure that user "B" has WRITE permissions to this directory.
          3. Deploy Tool writes its preferences into "iasdir/ias/dt". If user "B" needs to save the preferences, this directory needs to be WRITABLE by user "B". This permission is not critical for normal functioning of Deploy Tool.
          4. User "B" needs to have READ and EXECUTE permissions to many other directories/files as Deploy Tool loads/runs scripts/executables/executable jars/libs/dlls, and so on from iasdir/ias/bin, iasdir/ias/lib, iasdir/ias/java/classes (on Unix platforms) and others.
          5. As an additional precaution, user "B" needs to have WRITE permission to the directory where the app/module being opened resides on file system. For example, bank.ear resides in iasdir/ias/ias-samples/bank. Consequently, that directory should be WRITABLE.

          Database Support Issues

          This section describes the known iPlanet Application Server, Enterprise Edition 6.5 database support issues, and the associated workarounds.

          ID Summary
          -
          Problem
          Personal Edition of Oracle is not supported on Unix platforms.
          4639241
          Problem
          Vendor specific parameters, such as global connection, servername, databasename, ifxinformixhost, etc., are not saved when datasource is registered using XML file.

          Workaround
          The vendor-specific property cannot be specified using iPlanet Application Server 6.0 SPx XML files. You cannot mix parameters between the old and new XML files.
          Register the datasource using the new XML file.
          PointBase Database Installation (Unix Platforms)
          Problem
          The PointBase database installation requires access to the X Windowing System environment. If you are installing the PointBase database with the application server, the installation should have access to an X Windowing System. If there is no access to the X Windows environment, the PointBase database server will fail to start-up on that machine.

          Workaround
          When you attempt to install the Pointbase Database, you must have access to an X Windowing System Server, and in particular, have the DISPLAY environment variable set to point to that accessible server.

          If the DISPLAY variable is set incorrectly, iPlanet Application Server post installation commands fail.
          4643903
          Problem
          On Unix platforms, you will be unable to use the Oracle OCI driver if it has been registered under External JDBC Driver, through the Administration Tool.
          Workaround
          Ensure that $ORACLE_HOME is set in the iasenv.ksh script, under iASInstallDir /ias/env directory.

          Internationalization Issues

          This section describes the known iPlanet Application Server, Enterprise Edition 6.5 internationalization issues, and the associated workarounds.

          ID Summary
          4663565
          Problem
          When invoking Deployment Tool from the command line in Ja locale, an exception is thrown.
          4668770
          Problem
          Multibyte cookies retrieved using get and set methods appears as garbage in a browser.

          Sample Application Issues

          This section describes the known iPlanet Application Server, Enterprise Edition 6.5 sample application issues, and the associated workarounds.

          ID Summary
          4640249
          Problem
          Session distribution of soap web application does not work as per sample application documentation.

          Workaround
          In the soap-install.html file, under "Deploy the Apache SOAP Web Application" the third point should read:
          Select the WAR file from the list of Web Applications. Right-click and select Edit Descriptor from the pop-up menu. In the iAS tab, click the Distributed Session button so that it is unselected and click the Local Data Synchronization radio button so that it is selected. Since the Apache SOAP implementation stores non-serializable objects in user session, this step is required to disable session synchronization for the SOAP web application. Close the deployment descriptor window and be sure to save its contents.
          549549
          Problem
          Samples fail after recreating tables in PointBase.

          Several of the J2EE Developer's Guide samples require that you to recreate the database tables before executing the samples a second time. If you use the SQL files provided to recreate the tables without restarting the application server, several of the J2EE Developer's Guide samples will fail.

          Workaround
          For those samples that require recreation of database tables before running the samples a second time, restart iPlanet Application Server after recreating the tables.

          548418
          Problem
          "Inserted value too large for column" errors when using Bank application.

          Workaround
          Avoid using special characters or ` - ' for SSN or Phone number fields. Do not enter more than two letters for the State field and not more than four letters for the Prefix field.

          558611
          Problem
          Cannot create new customer in Bank Application with the same SSN of a deleted customer.

          The Bank Application does not correctly update tables in the database, and therefore you cannot create a new customer with same SSN.
          548861
          Problem
          iPlanet Type 2 Native Drivers for Sybase gives errors with JPS 1.1.2.

          Workaround
          Use a Sybase Type 4 driver to exercise JPS 1.1.2 with Sybase. The sample has been tested with the Sybase jConnect type 4 driver.

          549374
          Problem
          The setup_syb.bat and setup_syb.sh scripts for the Transactions sample will not execute.

          Workaround
          The path to isql in the script is wrong. Open the script with a text editor. Search and replace SYBASE/bin/isql with SYBASE/OCS-12_0/bin/isql .

          550427
          Problem
          Documentation error in the J2EEGuide sample.
          In the chapter "Currency Converter EJB", the third point under "Assemble EAR File", the value of the context root of the web application, is incorrectly mentioned as j2eeguide-confirmer .

          Workaround
          Replace j2eeguide-confirmer with j2eeguide-converter

          -
          Problem
          Documentation error in the Bank sample.
          Under the "Create bank.war Module" > "Modify Web Application Descriptor" topic, the login information in the "Security Tab" point is incorrect.

          Workaround
          When assembling the Bank sample application from scratch, the two lines for BankUser and BankAdmin have to placed together on one line.

          545753
          Problem
          Search functionality does not work when using JPS 1.1.2 with PointBase.
          Search functions do not work in JPS 1.1.2 when using the bundled PointBase database engine as the current version of PointBase bundled with iPlanet Application Server 6.5 does not support subqueries.
          560667
          Problem
          Exception while running l10n application
          An exception is thrown when the user logs in as restaurant owner.
          562432
          Problem
          Hot deployment of Petstore Application throws exception.

          Workaround
          1) Disable dynamic reloading, or
          2) Avoid making changes to the application when dynamic reloading is enabled.
          -
          Problem
          When iPlanet Application Server is installed with Microsoft IIS Webserver running on port number other than 80, the shortcut link for Sample Application will not work.

          Workaround
          Change the port number from 80 to the port number being used by IIS in the path-property for that shortcut.

          Uninstallation Issues

          This section describes the known iPlanet Application Server, Enterprise Edition 6.5 uninstallation issues, and the associated workarounds.

          ID Summary
          4538866, 4675352
          Problem
          iPlanet Application Server uninstaller does not stop the web server, resulting in numerous 'file busy' errors.

          Workaround
          Manually stop the web server before uninstalling iPlanet Application Server.

          Documentation Issues

          This section describes the known iPlanet Application Server, Enterprise Edition 6.5, documentation issues and the associated workarounds.
          ID Summary
          4537538
          Problem
          Task description about load balancing procedures is incomplete.
          In iPlanet Application Server Administrator's Guide, Chapter 14, "Balancing User-Request Loads ", the instructions do not specify to restart the Web server.

          Workaround
          Changes to the load balancing scenario requires that the application server and WebConnector Plugin (Web Server) be restarted.
          4639475
          Problem
          Documentation on uninstallation does not list all the directories left after uninstall.

          Workaround
          Some of the directories and files created by the installer, and those created by the user are not removed during uninstallation. Typically, the following directories are left after uninstallation:

          • admin-serv
          • httpacl
          • ias_APPS
          • pointbase
          • setup
          • bin
          • ias
          • lib
          • shared
          • README.txt
          You can manually delete these files.
          -
          Problem
          Documentation on dynamic reloading incorrectly states that, "whenever a reload is done, the sessions at that transit time become invalid".

          When reloading is enabled, there's no effect on HTTPSession established in the application.

          For example, consider an application that has three servlets- login servlet, processServlet, and logout servlet. If the processServlet is changed after accessing the login servlet, the user can still give a request to processServlet and get a new implementation of processServlet.

          How to Report Problems

          If you have problems with iPlanet Application Server, Enterprise Edition 6.5, contact iPlanet customer support using one of the following reporting mechanisms:
          • iPlanet online support web site at http://www.iplanet.com/support/online/
            • From this location, the CaseTracker and CaseView tools are available for logging problems.
          • The telephone dispatch number associated with your maintenance contract
          To assist you in the best possible way to resolve your problems, please have the following information available when you contact support:
          • Description of the problem, including the situation where the problem occurs and its impact on your operation

          • Machine type, operating system version, and product version, including any patches and other software that might be affecting the problem

          • Detailed steps on the methods you have used to reproduce the problem

          • Any error logs or core dumps

          Additional Information

          Useful iPlanet information can be found at the following Internet locations:

          Use of iPlanet Application Server, Enterprise Edition is subject to the terms described in the license agreement accompanying it.

          Copyright © 2002 Sun Microsystems, Inc. All rights reserved.

          Last Updated May 10, 2002