Sun ONE logo    
Release Notes for Sun ONE Web Server 6.0 Service Pack 3
816-6380-10
Updated: December 16, 2002



Release Notes for Sun(TM) Open Net Environment (Sun ONE) Web Server

Version 6.0 SP3

These release notes contain important information available at the time of release of Sun™ ONE Web Server 6.0 Service Pack 3 (formerly iPlanet™ Web Server Enterprise Edition 6.0 Service Pack 3). New features and enhancements, installation notes, resolved issues, and other late-breaking issues are addressed here. Read this document before you begin using Sun ONE Web Server.

Sun ONE Web Server Server 6.0 Service Pack 3 can be installed on the following platforms: HP-UX, Windows, Linux and Solaris™ Operating Environment (Solaris OE). For operating system details, refer to the section Sun ONE Web Server 6.0 SP3 Supported Platforms in these release notes.

These release notes contain the following sections:

Features Supported in Sun ONE Web Server Version 6.0 SP3

Sun ONE Web Server 6.0 SP3 offers the following features:

Sun™ ONE Active Server Pages Support

Sun™ ONE Active Server Pages (formerly, Sun™ Chili!Soft ASP) version 3.6.2 now supports the Sun ONE Web Server on Solaris, Windows, Linux and HP-UX. Sun ONE Active Server Pages Software is a server-side scripting and runtime environment for the cross-platform deployment of Active Server Pages (ASP or .asp) Web sites and Web applications.

Sun ONE Web Server 6.0 SP3 bundles Sun ONE Active Server Pages version 3.6.2 for Solaris, and Sun ONE Active Server Pages version 3.4.2 for Windows 2000. Sun ONE Web Server 6.0 SP3 also supports Sun ONE Active Server Pages version 3.6.2 on Windows. To use Sun ONE Active Server Pages version 3.6.2 on Windows, download the software from the following site:

http://www.chilisoft.com/downloads/default.asp

A licence is not required for Sun ONE Active Server Pages for Windows or Solaris if you are installing to the Sun ONE Web Server.

The Sun ONE Active Server Pages installer is available in the /plugins/chilisoft directory in the Sun ONE Web Server 6.0 SP3 download. When you install Sun ONE Web Server 6.0 SP3 on Windows or Solaris, the Sun ONE Active Server Pages installer is written to the directory:

%server_root%/plugins/chilisoft/


Note

If you are installing Sun ONE Active Server Pages, keep in mind the following points:

  • The Sun ONE Active Server Pages plug-in requires an additional 46MB of disk space after Sun ONE Web Server 6.0 SP3 is installed.

  • Before you begin installation, make sure you are logged in as root.

For more information on Sun ONE Active Server Pages, refer to http://www.chilisoft.com

Sun™ ONE Studio 3.0 Support

Sun ONE Web Server 6.0 SP3 supports Sun ™ ONE Studio 3.0 (formerly, Forte™ for Java™ 3.0). Sun ONE Studio 3.0 software is Sun's powerful, extensible, integrated development environment (IDE) for Java technology developers. It is based on the NetBeans™ Tools Platform, and it is integrated with the Sun Open Net Environment (Sun ONE). For more information and documentation on using Sun ONE Studio 3.0, please visit:

http://www.sun.com/software/sundev/previous/ffj/

Trustbase Support

Sun ONE Web Server 6.0 SP3 now supports Sun™ ONE Trustbase™ Transaction Manager on Solaris, which helps financial institutions provide trade facilitation services to their corporate customers. The product provides a common security infrastructure to multiple applications by routing messages between identity services and back-end systems. For financial institutions who are members of Identrus, the product includes an implementation of the Identrus Transaction Coordinator specification.

To receive the Trustbase plug-in for the Identrus system, send an email to trustbaseplugin@sun.com and you will be sent the URL for the download.

magnus.conf Directive Enhancement

The magnus.conf directive KeepAliveQueryMeanTime  can be used to tune keep-alive  subsystem performance. KeepAliveQueryMeanTime  specifies the desired keep-alive latency in milliseconds. The default value of 100 is appropriate for almost all installations. Note that CPU usage will increase with lower KeepAliveQueryMeanTime  values.

A magnus.conf  directive ServerString  has been added to allow administrators to change the Server  header in a response. An empty string, "", will cause the header to not be sent at all. Example:

ServerString "My Server ver. 1.0"

Windows 2000 Support

Sun ONE Web Server 6.0 SP3 supports Windows 2000 Server, Advanced Server, and Professional Edition SP2. At least 512MB RAM and 2GB of disk space is recommended for running Windows 2000.

Keep-Alive Subsystem Enhancement

The keep-alive  subsystem has been enhanced to now handle thousands of persistent connections.

JDK™ 1.3.1 Support

Sun ONE Web Server 6.0 SP3 works with JDK™ 1.3.1 on all platforms.

Virtual Server Report Generation

This user interface allows you to generate reports for specific virtual servers. You can access this page from the Logs tab of the Virtual Server Manager.

Web Application Deployment and Management User Interface

You can deploy web applications from the user interface as well as from the command line using wdeploy. New user interfaces have been added to the server manager to facilitate:

  • Web application deployment on a local machine or remote server machine

  • Web application editing for a virtual server

Role Mapping Support

Sun ONE Web Server 6.0 SP3 supports roles if the underlying LDAP server supports roles. If you wish to authenticate roles, you need to add the following to the server-id/config/web-apps.xml  file:

<role-mapping map-to="role" />

For more information about role authentication provided by iPlanet Directory Server 5.0 SP1, see:

http://docs.sun.com

web-apps.xml Data Type Descriptor

Sun ONE Web Server 6.0 SP3 allows you to enable or disable a web application. You can do so in either of the following ways:

  • Using the Application GUI: If you have already deployed a web application, select the Virtual Server instance that is running the application, and click Manage. Select the Web Applications tab, and click Edit Web Applications. From the Web Application State drop-down menu, choose from the options provided: Enable, Disable, and Delete.

  • At the web-apps level: By default, an application is automatically enabled with the value set to true in the server-id/config/web-apps.xml file. You can disable the application by setting the value to false.

    • Example:

    <web-app uri="/catalog" dir="/export/apps/catalog" enable="false">

    </web-app>

    For more information on iPlanet Web Server 6.0 DTD, see:

    http://developer.iplanet.com/webserver/dtds/iws-webapps_6_0.dtd

Single Sign-on Across Multiple Web Applications with FORM Login

Sun ONE Web Server 6.0 SP3 allows single sign-on across multiple web applications using FORM login configuration. You can enable this feature in two ways.

Configuring a session manager at the virtual server level

This is the easiest approach, but the session and session attributes are shared across all applications. Example:

<vs>
<!-- configure a VS-level session manager -->

<session-managerclass='com.netscape.server.http.session.IWSSessionManager'>

<init-param>
<param-name>maxSessions</param-name>
<param-value> 1024 </param-value>
</init-param>
<init-param>
<param-name>reapInterval</param-name>
<param-value> 8 </param-value>
</init-param>
<init-param>
<param-name>timeOut</param-name>
<param-value> 300 </param-value>
</init-param>
</session-manager>
</vs>

Configuring a virtual-server form-login session manager in a separate HTTP session

In this case, all form-login sessions are created using this VS-wide form-login session manager, and the container uses a separate cookie to track the sessions. These sessions are available across all applications within the virtual server.

The VS-wide form-login session manager is created when a form-login-session element is present under the vs element in the server-id/config/web-apps.xml file. You can customize the underlying session manager, cookie name, and the session timeout using the form-login-session element. Example:

<vs>
<!-- configure form login session timeout to 300 secs (5 min), with
MMapSessionManager -->
<form-login-session timeOut="300">
<session-managerclass='com.netscape.server.http.session.MMapSessionManager'>
<init-param>
<param-name>maxSessions</param-name>
<param-value>10000</param-value>
</init-param>
<init-param>
<param-name>reapInterval</param-name>
<param-value>8</param-value>
</init-param>
</session-manager>
</form-login-session>
</vs>

The advantages of configuring a virtual-server form-login session manager in a separate HTTP session are:

  • The form-login session manager can be different from the per-web application or VS-wide session manager.

  • Session data is not shared across web applications when single sign-on is enabled, since a separate session manager is used for FORM login.

  • The user principal is not available as a session attribute, since it is stored in a private session.

The drawbacks of configuring a virtual-server form-login session manager in a separate HTTP session are:

  • Session tracking via URL does not work; only cookie tracking is supported.

  • Per-web application session timeout and session cookie configuration are not supported by the form-login session

  • You cannot implement logout using session.invalidate().

Localized Version Support

By installing Sun ONE Web Server 6.0 SP3 over an existing iWS 6.0 SP1 install, you can take advantage of the localization support provided by iWS 6.0 SP1, available in Japanese, French, German and Spanish.

Support for Arbitrary Custom Headers

In Sun ONE Web Server 6.0 SP3, the set-variable SAF (Server Application Function) can be used to add custom headers to the server's HTTP responses. For example, consider the following server-id/config/obj.conf directive:

AuthTrans fn="set-variable"
insert-srvhdrs="P3P:policyref=\"http://hostname/P3P/policy.xml\""

This directive instructs the server to add the following HTTP header to each response:

P3P:policyref="http://hostname/P3P/policy.xml"

Support for Response Header Encoding

Sun ONE Web Server 6.0 SP3 supports two byte character response header encoding in HTTP header and plugin programs.

PHP Compatibility

Sun ONE Web Server 6.0 SP3 is compatible with PHP, the versatile and widely-used Open Source general-purpose Web scripting language that allows server-side scripting, command line scripting, and client-side GUI scripting. PHP runs on all major operating systems. The following section tells you where you can find PHP-specific installation and configuration information:

Installation Instructions

For platform-specific installation instructions, refer to the following sites:

For general installation instructions, see:

http://www.php.net/manual/en/installation.php

Sun ONE Web Server (formerly, iPlanet Web Server) Install Notes

For installation and configuration information that is specific to the Sun ONE Web Server installs of PHP, refer to the following:

http://www.php.net/manual/en/install.netscape-enterprise.php


Note

The configuration information in the site http://www.php.net/manual/en/install.netscape-enterprise.php  is accurate for iPlanet Web Server 4.x. For iPlanet Web Server 6.0 and above however, you need to make the specified changes to the Init function in the server-id/config/magnus.conf  file, and not the server-id/config/obj.conf  file.

For more information on PHP, see the following sites:

Required Patches

Required patches are listed for the following platforms:

Sun Solaris Patches

If you are using a JRE that is different from the one bundled with Sun ONE Web Server 6.0 SP3, or if you are using a JDK, you might need additional patches.

The following patches are recommended for Solaris users of Sun ONE Web Server. In addition, you should have the patches in Sun's recommended patch list. For Sun's recommended patch list, see http://sunsolve.sun.com/pubpatch. You can download Sun patches from http://sunsolve.sun.com.

For each patch, use the listed revision or a higher revision. For example, if you need patch 111111-01, the later revision 111111-03 will also work.

Solaris 2.6

The following patch is required to run iPlanet Web Server 6.0, on Solaris 2.6:

  • 105591-09


    • Note

    You can determine if you have the patch by running the following command:

    % showrev -p | grep 105591

Solaris 7

Use the latest Solaris patches for Solaris 7.

Solaris 8

Patch 108727-05 is required for Solaris 8 users with NFS volumes.

Solaris 9

No patches required.

Compiler Patches for Solaris

The following Solaris 2.6 patch is recommended when using the CC 4.2 compiler:

  • 104668-09.

HP-UX Patches

In addition to using the General-Release Patch Bundles (XSWGR1100), the following operating system patch (applicable and specific to HP-UX 11i, 11.11 only) must be installed: PHNE_23645.

You can find a list of patches for Java 1.2.2.07 at:

http://us-support.external.hp.com/

Windows Service Packs

Windows NT 4.0 SP6A is required for running iPlanet Web Server 6.0.

Windows 2000 Server SP2 or later is required for running Sun ONE Web Server 6.0 SP3.

JRE/JVM Versions

The following versions of JRE and JVM are bundled with Sun ONE Web Server 6.0 SP3:

Table 1    JRE and JVM Information

Platform

JRE /JVM /JIT Version

Comments

Solaris 2.6, 8,9

Solaris VM Java version 1.2.2

(build Solaris_JDK_1.2.2_010, native threads, sunwjit)

Comment out -Xrs flag in config/jvm12.conf to generate stack traces.

For JVMPI based profiling or debugging purposes (such as with hprof or dbx) purposes, use the reference implementation downloadable from:

http://java.sun.com/products/jdk/1.2/

The default JDK on Solaris 9 is JDK 1.4. In order to run Sun ONE Web Server 6.0 SP3 on Solaris 9, create a link to JDK 1.2 located in /usr/java1.2/bin/java.

Windows NT 4.0, Windows 2000

Java version 1.2.2 Classic VM

(build JDK-1.2.2_010, native threads, symcjit)

None

HP-UX

Java version 1.2.2.10 HotSpot VM

(1.0.1fcs, mixed mode, PA2.0 build 1.2.2.10-01/09/14-PA_RISC2.0)

The Sun ONE Web Server 6.0 SP3 download also contains Java version 1.2.2.10 Classic VM.

(build 1.2.2.10-01/09/14-PA_RISC2.0, native threads, HP)

For more information on the HotSpot VM, see:

http://www.hp.com/products1/unix/java/ java2/sdkrte/downloads/license_sdk_1-2 -2-10.html

Linux

Java version 1.2.2 Classic VM

(build Linux_JDK_1.2.2_FCS, native threads, sunwjit)

For optimal performance, use JDK 1.3.1, downloadable from the following sites:

For more information about JVM/JRE version 1.2.x for Solaris, go to:

http://www.sun.com/software/solaris/java/download.html

Installation, Upgrade, and Migration Information

This section includes information for installing, upgrading, and migrating your Sun ONE Web Server.

The following table summarizes the supported platforms for Sun ONE Web Server 6.0 SP3. To successfully run Sun ONE Web Server 6.0 SP3 on Windows 2000, at least 512 MB of memory and 2 GB of disk space are required.

Table 2    Sun ONE Web Server 6.0 SP3 Supported Platforms

Vendor

Architecture

Operating System

Hewlett-Packard

PA-RISC

HP-UX 11.0, 11.0 64-bit*, 11i*

Microsoft

Intel x86

Windows NT 4.0 SP6a

Windows 2000 Server SP2

Sun

UltraSPARC**

Solaris 2.6, 7*, 8, 9

Linux

Intel x86

  1. Red Hat Linux 6.2

Linux version 2.2.14-12

glibc-2.1.3-15

  1. Red Hat Linux 7.1 2.96-79

glibc-2.2.2-10

libncurses.so.4

*Supported via binary compatibility.

**As of iPlanet Web Server 6.0, older SPARC CPUs are not supported. Sun ONE Web Server 6.0 SP3 continues to support the UltraSPARC architecture.

Upgrade Issues

If you are running a 4.x version of iPlanet Web Server, in order to move to Sun ONE Web Server 6.0 SP3, you must migrate your existing server. However, if you have a 6.x version of iPlanet Web Server, you can directly upgrade to Sun ONE Web Server 6.0 SP3.

Resolved Issues

This section contains lists of issues resolved in the following service pack releases:

Issues Resolved in SP3

This section lists issues resolved in Sun ONE Web Server 6.0 SP3.

Problem 4674755. Buffer overflow issues with iws6.x.

Buffer overflow issues with the Search functionality have been resolved in Sun ONE Web Server 6.0 SP3.

Problem 4536410 (562171). SSL: Runtime Error occurring when select any cert Manage Certificate on IE.

The runtime error message was specific to Internet Explorer 5.5, which is no longer available for download. It does not appear with IE 5.5 Service Pack 2 or any other version of Internet Explorer.

Problem 4536442 (562558). Virtual Server: Server Error Encountered when Disable ACL Access Is On.

As of Sun ONE Web Server 6.0 SP3, even if access control is disabled at the server level, virtual servers irrespective of what class they are under, function properly.

Problem 4536399 (562134). Cannot Use Distributed Admin over LDAP with SSL.

As of Sun ONE Web Server 6.0 SP3, if the CA certificate is properly installed, Distributed Administration works smoothly with LDAP over SSL. For more information on installing the CA certificate, see the chapter "Securing Your Web Server" in the Administration Guide.

Problem 4541660 (525692). Cannot Add a Cluster That is Under SSL.

As of Sun ONE Web Server 6.0 SP3, you can add a server to the cluster under SSL.

Problem 4536879 (553613). Monitor Current Activity: Cannot Monitor SSL-enabled Server.

Sun ONE Web Server 6.0 SP3 enables proper monitoring of the current activity of SSL-enabled servers.

Problem 4582824. 2 byte character in http header and plugin programs.

As of Sun ONE Web Server 6.0 SP3, you can enable response header encoding at either the web-app level or the virtual server level by setting the value of the configuration parameter use-responseCT-for-headers to any of the values, yes, true, or on, in the server-id/config/web-apps.xml file. The web-app setting overrides the virtual server level setting.

In the following example, response header encoding is disabled at the web-app level by setting the parameter value to false:

<vs>

<config-param>

<param-name>use-responseCT-for-headers</param-name>

<param-value>on</param-value>

</config-param>

<web-app uri="/jakarta" dir="/export/home/ramach/Rtm1026/ns/server/work/B1/Sun

OS5.6_DBG.OBJ/docs/jakarta" enable="true">

<config-param>

<param-name>use-responseCT-for-headers</param-name>

<param-value>false</param-value>

</config-param>

</web-app>

</vs>


Note

If you are using legacy servlets, to enable response header encoding, set the value of the parameter context.global.use-responseCT-for-headers  to  true  in the server-id/config/context.properties file. To disable this feature, set the parameter value to false.

Due to a browser issue, when you use the Korean character set, a version 4.7 or later Netscape browser, on Solaris 2.8 fails to display characters properly in the "File Save" dialog box. A bug has been filed with Netscape Communications Corporation. For more details, see:

http://bugzilla.mozilla.org/show_bug.cgi?id=144995

As of this release, setting the value of the urlencoding parameter in the function index-common in the server-id/config/obj.conf file to off, enables index listing of encoded directories. Example:

Service method=(GET|HEAD) type=magnus-internal/directory fn=index-common urlencoding="off"

Problem 4539568. Unable to create ACL under non SSL webserver with SSL LDAP server.

If your Sun ONE Web Server installation is configured to use an SSL LDAP server, you must also ensure that it has at least one of the following:

  • Server Certificate Chain

  • Trusted Certificate Authority

As of Sun ONE Web Server 6.0 SP3, in case of a bind failure, you will receive an LDAP bind error message.

Problem 4653116. Need to update appendix on data structures in the NSAPI Programmer's Guide.

As of Sun ONE Web Server 6.0 SP3, the NSAPI Programmer's Guide contains a new section titled "Changes to function Flow" which discusses conditions that cause changes in the normal request handling process. Additionally, the section on the request  data structure in the appendix on data structures has been updated.

Problem 4537817. ADM:web-apps: should add a "Remove" option under state section.

As of Sun ONE Web Server 6.0 SP3, if you do not specify the name of a web-apps file associated with a web application, when you delete the web application, the corresponding web-apps file is automatically deleted, and its associated entry in the server.xml  file removed. Before deletion, however, you must ensure that no other server instance is referencing the web-apps file associated with the application you want to delete.

Problem 4527108. >51 entries in a specific .htacess file format causes server restart.

As of Sun ONE Web Server 6.0 SP3, in a .htaccess file, if the number of require  directives exceeds 50, or if the number of entries under the allow or deny directives exceeds 50, subsequent entries are ignored, and an error is logged in the error log file located in https-server_name/logs/errors  in the server root directory.

Problem 4536034. Implement verbose:gc option to work with iWS.

As of Sun ONE Web Server 6.0 SP3, the values allowed for the jvm.verboseMode  parameter are gc, class  and  jni, with the default being gc. Please note that the parameter values are case-sensitive.

Problem 4672869. MBCS version Windows 2K: appending jsp with %81 to %99 displays source code.

If Sun ONE Web Server 6.0 SP3 is running on a Windows system using the multibyte character set, when you specify a URI, ensure that the path component of the URI (that is, the path, the filename, and the path-info, but not including the query) is less than or equal to 257 bytes.

For example, in the URI /cgi-bin/printenv.pl/foo/bar?name=value, the path to the resource (/cgi-bin/printenv.pl) and the path-info (/foo/bar) together must not exceed 257 bytes.

Problem 4551521 (554201). HP-UX: Heap Grows Linearly in HP with >24 Hour Stress Test.

As of Sun ONE Web Server 6.0 SP3, the parameter jvm.stickyAttach  is by default set to 1 in the jvm12.conf  file, and the memory footprint growth is under control.

Problem 4638330. Possible vulnerabilities reported on security advisor on SNMP.

Sun ONE Web Server 6.0 SP3 has been enhanced to provide robust and secure SNMP trap handling and request handling support.

Problem 4655840. ACL cache broken with the SSL method of ACL authentication.

Problem 4623309. root CA certificate is not imported correctly in iWS 6.0.

Problem 4624104. Crash occurred in NSAPI SAF send-cgi.

Problem 4624881. Servlets: iWS adds additional Connection header to responses.

Problem 4633588. Role base authentication does not work for web applications deployed with root directory as the URI.

Problem 4548524 (558970). Silent Installation: Option Added for Port Numbers.

Problem 4549431 (554941). Installing Subcomponent 2, 4, or 5 on Top of iWS 6.0 SP1 Produces Error.

Problem 4549640 (555532) (Windows only). Installation: Unable to Load JVM.

Problem 4549406 (554863). Silent Installation Broken When Installing iWS 6.0 SP1 on Top of iWS 6.0.

Issues Resolved in SP2

This section lists issues resolved in iPlanet Web Server 6.0 SP2.

Problem 556138. Keep-alive Subsystem Shows High Latencies Under Light Load and High CPU Usage Under Heavy Load.

As of iPlanet Web Server 6.0 SP2, latencies under very light load have been reduced while increasing throughput under very heavy load. Please see Keep-Alive Subsystem Enhancement section in the SP2 Release Notes to see how this is done.

Problem 548237. Allow Behavior /Feature Modifications Based upon User-Agent.

As of iPlanet Web Server 6.0 SP2, the <Client> tag can be used in obj.conf  files to customize behavior for specific browsers. For example, the following obj.conf  directives instruct iPlanet Web Server to serve different content based on whether the user is using a Microsoft Internet Explorer (MSIE) browser:

<Client browser="*MSIE*">
NameTrans fn="document-root" root="$docroot/MSIE"
</Client>
NameTrans fn="document-root" root="$docroot"

Problem 532427: SSL Interoperability with Microsoft Internet Explorer

The way Microsoft Internet Explorer (MSIE) handles SSL version 3 (SSLv3) and Transport Layer Security (TLS) keep-alive connections causes interoperability problems with non-Microsoft web servers such as iPlanet Web Server. When accessing a web server over SSL (https://) connections, Internet Explorer may inappropriately display error messages or blank pages.

iPlanet Web Server 6.0 SP2 introduces new functionality to work around this problem. Two remedies are possible:

  1. Add the following line immediately below the <Object name="default">  line in the server's obj.conf  files:

    2. AuthTrans fn="match-browser" browser="*MSIE*" ssl-unclean-shutdown="true"

This line instructs the server to not send a close_notify  alert when it closes SSLv3 connections from MSIE browsers. The close_notify  packet is a required component of the SSLv3 and TLS specifications, but it is misinterpreted by MSIE.

Note that the close_notify  packet is used in SSLv3 and TLS connections to inform the other party in the transaction that the connection is being closed. Instructing iPlanet Web Server to not send the close_notify  packet may make MSIE vulnerable to a truncation attack.

  1. Add the following line immediately below the <Object name="default">  line in the server's obj.conf  files:

    2. AuthTrans fn="match-browser" browser="*MSIE*" keep-alive="disabled"

This line instructs the server to disable keep-alive connections for Internet Explorer browsers. Disabling keep-alive connections may decrease your server's performance.

Problem 550648 (NT only). Silent Installation: Broken on NT.

Problem 556697. Server Instability with `AsyncDns on' in magnus.conf.

Problem 553079. SSL: Should place rsa_rc4_128_sha in order.

Problem 555848. Misleading SSLPARAMS error message.

Problem 555347. WDEPLOY GUI: Shouldn't allow to deploy 2 identical URI to 2 different directories.

Problem 551863. wdeploy doesn't create directory (under document root) when -d is omitted.

Problem 555814. WDEPLOY GUI: Internal Error when user re-enter "empty" for URI.

Problem 557009. wdeploy.bat does not work if IWS_SERVER_HOME has spaces (e.g. "C:\\Program Files\...").

Problem 559051. WDEPLOY GUI: User shouldn't allow to edit 2 identical URI.

Problem 548386. Administration problems when installation path contains a space.

Problem 555875. Web Application Sample: Missing little icon at some servlet example files (jakarta-examples).

Problem 552008. WDEPLOY: filename of invalid .war file is not reported.

Problem 553841. <Client> tag functionality.

Problem 552206. ClassCache directory should have Version file when an instance is added.

Problem 555373. Need to Support Extension Mappings for url-patterns in security-constraint.

Problem 551333. getInputStream.available() throws exception despite having a valid content.

Problem 552908. Fix form-login session manager behavior.

Problem 540088. Web applications should support iDS5.0 roles.

Problem 557875. SP1 regression: automatic reloading of web application servlets not working.

Problem 555913. Server crashes when a request is made to servlet/ of a web application that has an invoker servlet configured.

Problem 557270. web.xml <session-config> does not override web-apps.xml configuration for VS-wide session managers.

Problem 552758. Init directives in magnus.conf can't span lines.

Problem 554676. Reconfiguration error when server is started as root but run as a different user.

Problem 559204. Templatized installation fails if hostname has a hyphen (-) in it.

Problem 556730. iWS6.0 SP1 uninstall at ion does not stop the running processes.

Problem 554801. Admin: Create a new access log from the UI does not work correctly.

Problem 555144. UI: Add server page for NT and W2K should be improved.

Problem 556134. Migration: Inconsistency between platforms for Manage Server.

Problem 555978. UI: View button on Cluster Control does not work for Nav.6.01.

Problem 555517. Timeout is not working properly for chunked requests.

Problem 556529. Windows Installer: License file formatting is bad without any word wrap.

Problem 558681. Cluster Management - UI: Status field shows wrong status during server restart.

Problem 554488. Admin: Unable to generate report for a VS on certain cases.

Problem 554491. Admin: NT, Some types on mime.types are repeated.

Problem 557679. Upgrading 6.0 to 6.0SP1 results in multiple entries in start -jvm.

Problem 354145. Viewing large logs from the administration server is slow.

Problem 557652. Server should ignore MaxProcs setting on NT.

Problem 557285. Long error log lines hard to read in Administration Server.

Problem 553737. AcceptLanguage isn't migrated.

Problem 557765. nsapi.h has incorrect vs_is_default_vs() macro.

Problem 553002. Intermittent fork() hangs when accessing files over NFS.

Problem 558278. Crash with misconfigured LDAP entry in dbswitch.conf.

Problem 556642. License file has an extra blank line.

Problem 546926. Search engine does not index certain hi-bit characters.

Problem 556074. DOC: StrictHttpHeaders default value is on.

Problem 559705. Admin: Global|SNMP Master Trap Warning displays "managerwhich" or "communitystring."

Problem 558501. Quotes not stripped from charset value.

Problem 553055. Need match-browser functionality.

Problem 557766. Allow stats-xml elements to be selectively disabled.

Problem 557278. Administration Server shows HTML code embedded in access log.

Problem 557461. iWS60 providing 400 bad request response for windows media content.

Issues Resolved in SP1

This section lists issues resolved in iPlanet Web Server 6.0 SP1.

Problem 550665. Specifying a Relative URI in a CGI Program's Location: Header Fails.

In previous versions of the server, CGI programs that wanted to redirect a browser to another location were forced to supply a URL, for example http://server/index.html, or an absolute URI, such as /index.html. Starting with SP1, relative URIs, such as index.html, are also accepted.

Problem 544444. No Way to Log Time Server Spent Processing Requests.

Prior to SP1 there was no way to log time the server spent processing requests. A new flex-log format variable, %duration%, has been added. %duration% records the time in microseconds the server spent handling the request. Statistics must be enabled for the server instance before %duration% can be used. See the iPlanet Web Server 6.0 Administrator's Guide for information on enabling statistics. For more information on log file formats, refer to the iPlanet Web Server 6.0 NSAPI Programmer's Guide and the iPlanet Web Server 6.0 Administrator's Guide.

Problem 550505. Server Does Not Track the Number of Times the Keep-alive Subsystem Was Full.

Prior to SP1 there was no way to track when the keep-alive subsystem was full. The server now tracks the number of times a connection was not added to the keep-alive subsystem because the keep-alive subsystem was full. This information is presented as KeepAliveRefusals  in .perf  output. For more information on .perf, refer to the iPlanet Web Server 6.0 Performance, Tuning, Sizing, and Scaling Guide.

Problem 549754. Cannot Use an Arbitrary URI as an Error Page.

Prior to SP1 it was not possible to use an arbitrary server resource, such as a JSP or SHTML page, as the error page. As of SP1, the parameter uri has been added to the send-error  Error SAF. uri  specifies the URI of a resource to use when an error is encountered.

Consider the following line from obj.conf:

Error fn="send-error" reason="Not Found" uri="/notfound.jsp" path="/usr/iplanet/servers/docs/notfound.html"

This line instructs send-error  to behave as though the client had requested /notfound.jsp  when the client requests a URI that does not exist. If an error is encountered when accessing /notfound.jsp, the HTML file at /usr/iplanet/servers/docs/notfound.html  will be displayed instead. For more information on the send-error  Error SAF, refer to the iPlanet Web Server 6.0 NSAPI Programmer's Guide.

Problem 554157. Search: Guided Search Screen Does Not Show Up Using IE. Problem 551659. Search: Guided Search Does Not Work Over SSL.

Problem 553775. JAVA: SECURITY Authentication Rules Broken Based on Role-mapping.

Problem 547682. JDK 1.3.1 Shuffled Parameters in Output Using Classic JVM.

Problem 551907. Filters Not Reloaded when the Classes in a Web Application Are Changed.

Problem 554353. Migration: Migration Page Throws Errors During Migration of Hardware Virtual Servers via virtual.conf

Problem 554465. wdeploy: Hard Delete Failed if Server Instance Not Running.

Problem 555730. Migration: Unable to Start Migrated Server Instance on NT.

Problem 546765. NCA Failure with Certain SAFs.

Problem 545375. VS: Using "any","ANY","INADDR_ANY" IP Could Not Select Matching IP.

Problem 545609. Hardware Virtual Servers Configured by obj.conf Do Not Get Migrated Properly.

Problem 552229. Web Application: Sample HelloWorld.war Needs Updating since the JAXP v1.1 Enforces DTD Conformance.

Problem 550920. getResource() Does Not Work on Resources Bundled in .jar files.

Problem 552001. WDEPLOY: Need to Have a Type Checking for the [-n] parameter.

Problem 551491. FileStore Fails to Report init Failure.

Problem 551144. New NSS Ciphers Are Automatically Enabled.

Problem 551103. Serialization Fix Causes JSP Recompilation Errors.

Problem 549900, 549774. Document Root Does Not Support Dash (-).

Problem 549762. Java Web Application Admin Screen Should Create Non-existent web-apps XML Files.

Problem 549749. wdeploy Does Not Work on VSs Other Than the Default One.

Problem 549618. VS: Couldn't Add Any Group Member when Select "any."

Problem 543265. Admin: Dist. Admin Default Prompt Should Not Be ' '.

Problem 538648. VS: Do Not Allow VS State "off" While It Is the Default VS.

Problem 543245. Distributed Administration Issues an Error When LDAP Server is Down, Cannot Get to Web Server Administration Server.

Problem 550847. Update JAXP XML Parser to v1.1 (currently 1.0.1).

Problem 551863. wdeploy Doesn't Create Directory (under document root) When -d Is Omitted.

Problem 549749. Session Failover/Persistence Does Not Work with Legacy Servlets.

Problem 551553. Migration - JSPs: Getting Servlet Service Exception When Migrating JSPs from iWS 4.1 to iWS 6.0.

Problem 552516. JAVA: Failure in Authenticating a Valid User.

Problem 549797. Session Tracking Failed When No Session Manager Is Specified.

Problem 543748. jvm.serializeFirstRequest=1 Not Working Correctly.

Problem 543882. URL-Pattern Suffix Matching Misses Intended Mapping.

Problem 549541. Dist Admin: Set ACL for Preferences to a Particular User Gives a `Permission Denied' when Click on Browse Button.

Problem 531704. NSAPI Configuration Doesn't Migrate from 4.X to 6.0.

Problem 537073 (NT only). Migrate Server Page Throws Errors.

Problem 542994. AsyncDNS is not Supported in this Release of the Server.

Problem 519936. Entering an Extra Space on the Listen Socket Generates an Error.

Problem 544385. Help for Clusters.

Problem. 544449. Cannot Change Groups Settings in Edit Listen Socket when Listen Sockets Table IP Is Set to `Any'.

Problem 544902. Virtual Server User Interface Does not Accept "." or "-" characters for Either the Listen Socket ID and the Virtual Server ID.

Problem 545947. Cannot Transfer magnus.conf to More than One Cluster at a Time.

Problem 535158. Unable to Stop the Server when using JDK version 1.2.2_07.

Problem 543691. Mail and News Collections Show Physical Path in URL.

Problem 539908. Unable to Generate Report for Server Statistics for Different Virtual Servers.

Problem 542976. Distributed Administration: Internal Error when "Allow end user access: = no".

Problem 543876. "method Not allowed" for Manage Language List.

Problem 543902. Administration Server User Interface does Not Show the Entry for an User While ACL File Does Indicate the Entry.

Problem 545568. With Distributed Administration, End User Access not Loading User Page on Login.

Problem 544902. (Solaris only) JVM Options: Default JVM Options Should Be Optimal.

Problem 545874. (Windows NT only). An Error May Occur When Creating or Maintaining a Collection

Problem 543196. (Windows NT only) System Hangs When Adding Two Collections.

Known Problems and Solutions

This section lists known problems with this release of Sun ONE Web Server 6.0 SP3. Information is organized into the following areas:

General

Problem 4693559. Invalid "Feedback" link in instance default home page.

Workaround

Send feedback on Sun ONE Web Server 6.0 SP3 to:

http://www.sun.com/service/support/software/iplanet/index.html

Problem 4652585. Enabling distributed admin disables the local admin user in 6.0.x.

Workaround

Before enabling distributed administration, create a user with the name and password of the local superuser  (the user name and password you specified during installation), and add it to the distributed administration group.

Problem 4659434. web-apps allows URI to be created as /search.

Workaround

Do not use reserved URIs to deploy web applications; for example, because /search  is a reserved URI, do not use it as a URI for deployment, otherwise you will not be able to access the Search functionality. For a list of reserved URIs, see the obj.conf  file directives in the iPlanet Web Server 6.0 NSAPI Programmer's Guide.

Problem 4658415. Large stack size causing problems with JVM in JDK 1.3.

Workaround.

Because stack size requirements of different JDK versions are different, if you are using a JDK version that is different from the default JDK bundled with Sun ONE Web Server 6.0 SP3, you might experience stack overflow problems. In case you do, edit the StackSize  directive in the server-id/config/magnus.conf  file to modify the stack size for the request handling thread. The stack size limits for JDK 1.2.2 (for Solaris) and JDK 1.3.1 are as follows:

  • JDK 1.2.2 (on Solaris)

    • Minimum allowed Java stack: 1000 bytes

    • Minimum allowed Native stack: 24 kb

  • JDK 1.3.1

    • Minimum allowed stack: 64 k

    • Default stack size: 512 k

Problem 4618374. iWS unnecessarily decodes cookies passed between the client and the server.

Workaround

To prevent default cookie encoding, change the value of the context.global.enableCookieEncoding  property in the server-root/server-instance/config/contexts.properties  file to  false.

Problem 4667303. Appending a backslash '\' in the server root path, while migrating the server, throws an invalid path error on a Windows 2000 server.

Workaround

During migration, ensure that a trailing backslash, if any, in the server root path is removed.

Problem 4637844. Cannot login to admin server, when run as non-root.

Workaround

If you need to run the admin server with a non-root userid, invoke setup with the same userid.

Problem 4551032. LDAP auth succeeds but ACL fails when presented credentials contain whitespace.

Workaround

During login, ensure that your username does not contain any white spaces, otherwise the authentication attempt will fail and an error will be logged in the server's /logs/errors  file.

Problem 554092. VS Command line: Should Add an Option for Accept Lang on/off When Creating VS CLASS.

A new optional parameter, acptlang, has been added for creating a virtual server class. You must add [-acptlang] to the command line to enable accept language header parsing for your server. The default is `off' if this parameter is not added.

Problem 549203 (Unix only). Setuid Cgistub Shouldn't Allow Execution of Root-owned Binaries.

As of SP1, the set-user-ID-on-execute (suid) Cgistub  will not allow a non-root user to execute programs owned by root. This change enhances the security of the suid Cgistub  system.

Workaround

If you require pre-SP1 functionality, log in as `root' and perform the following steps from a command line to modify the suid Cgistub  for instance https-instance  in server root server_root:

  1. Change to the instance directory:

    2. cd server_root/https-instance

  2. Stop the server

    3. ./stop

  3. Change to Cgistub's private directory

    4. cd private

  4. Allow root to write to the private directory

    5. chmod 700

  5. Tell Cgistub to trust programs owned by user 0 (root)

    6. ./Cgistub -s "trusted_uid 0"

  6. Disallow writes to the private directory

    7. chmod 500

  7. Change to the instance directory

    8. cd ..

  8. Restart the server

    9. ./start

Loading More Than 1000 Virtual Servers Slows Performance.

Adding more than 1000 software virtual servers under one class slows the loading of the Class Manager Members page.

Problem 549383 (Windows 2000 only). Cluster Management: Transfer File Hangs the Admin Server and Creates a 0KB File Size.

Files are transferred by the master of the cluster requesting the remote machine's admin to run clxfer. The clxfer  process of the remote machine requests the master to transfer the file, and the master runs clxfer  to return the file. The master receives the host name of remote machine from the request, and finds the required file in /cluster/hostname/instance-names. If, for example, a remote machine named `charis' is added to a cluster named `charis.india.sun.com', the request header with `charis' as host name will fail to find the file in `cluster/charis'. The remote machine will receive a 0 byte file due to the error.

Workaround

Ensure that all machines have the full name. To do that go to control panel -> system ->network identification -> property in your remote machine. Enter the primary DNS suffix to match the master machine.

Problem 546532 (Solaris only). Cannot Throw Exceptions from -compat=5 plug-ins.

Workaround

  1. When using version 5.0 or higher of the Sun/Forte WorkShop C++ compiler to create an NSAPI plug-in that throws exceptions, the -compat=4  option should be specified. This is necessary because, by default, WorkShop 5.0 generates object code that is not binary compatible with WorkShop 4.2 object code. Specifying -compat=4 makes newer WorkShop versions behave like version 4.2.

  2. If you are unable to specify -compat=4, add shlib_flags="(default|parent|group)" to your plug-in's Init fn="load-modules" line in  magnus.conf. For example:

    3. Init fn="load-modules" funcs="my-plugin" shlib="myplugin.so"

    shlib_flags="(default|parent|group)"

    Doing this will place your plug-in in its own dynamic link group. As a result, it will also be necessary to explicitly specify all your plug-in's shared object dependencies at link time. For example, your plug-in's CC command line might look like this:

    CC -G -lCrun -lm -DXP_UNIX -I/usr/iplanet/servers/plugins/include

    -o myplugin.so myplugin.cpp

Problem 517789. Deleting Class From Virtual Server Does Not Delete Entry From obj.conf File.

When a virtual server class is deleted from the Server Manager, Virtual Server Class, the obj.conf  file still shows the deleted class. However, the class is removed from the user interface and from the server.xml file.

Workaround

Manually remove the deleted class from the obj.conf  file.

Problem 538947. Use of conf_getglobals() in NSAPI Init Functions.

The following is an issue for NSAPI plug-in developers or for users of third party NSAPI plug-ins that have not been certified with iWS 6.0 by their developers.

  1. If you are the developer of an NSAPI Init function, here is the technical information needed to check if your plug-in suffers from this problem and if so, how to correct it:

    2. The use of the NSAPI conf_getglobals() function, or the various macros in the nsapi.h header file that refer to conf_getglobals(), is not recommended within NSAPI Init functions in iWS 6.0. conf_getglobals() can only return the properties of a single virtual server. In iWS 6.0, a single web server may have many virtual servers defined with completely distinct properties, such as port, hostname, and security. Also, the configuration of any virtual server in iWS 6.0 can dynamically change over time. Therefore, a plug-in should not attempt to retrieve and store the server configuration information during NSAPI Init time, but rather retrieve the configuration in an ephemeral way during request processing time, when the server configuration information is actually needed (e.g., to build links in a dynamic web page).

    The default behavior of conf_getglobals(), if called during Init in iWS 6.0 is to leave the following fields initialized with a default value (e.g., 0 , NULL): Vport, Vaddr, Vserver_hostname, Vsecurity_active, Vssl3_active, Vssl2_active, and Vsecure_auth. If your Init function relies on the values of these global fields but does not have error checking, it could crash and prevent the web server from coming up; or it could cause crashes at a later time if these null values are saved and later reused in other plug-in functions.

    If you are currently calling conf_getglobals() in your Init function, you should modify your code to eliminate any such calls. This will ensure proper operation of your plug-in in iWS 6.0 when multiple virtual servers exist. The conf_getglobals() NSAPI function will only return the proper values corresponding to the connection and virtual server on which the request was made if called during an NSAPI request processing phase - e.g., during an NSAPI AuthTrans, NameTrans, Service, or other NSAPI request processing phases.

    iWS 6.0 supports a compatibility mode for older plug-ins suffering from this problem. As noted in the user section, it requires the NSAPI Init functions to be marked as LateInit. When called

    from a LateInit Init function, conf_getglobals() will return the properties of the default virtual server of the default connection group of the legacy listen socket. In terms of the new XML configuration attributes, this means that conf_getglobals() now returns the properties of the defaultvs  of the defaultgroup  of the legacyls  of the SERVER. It is recommended that the server should only have that single virtual server defined in this case to ensure consistent server and plug-in operation.

  2. If you are the user of an NSAPI Init function of a plug-in developed by a third party, you should contact the plug-in developer to find out if it is compatible with iWS 6.0 based on the technical information for developers stated in 1. Many Init functions will not be affected and are expected to continue to function unmodified with iWS 6.0, however, the determination of compatibility and possible need for an update should be made by the plug-in developer.

    3. If your plug-in vendor does not certify their Init function for use with iWS 6.0, and the function is found to suffer from the specific programming problem described in 1., you may work around the problem if:

    • you only have a single listen socket, connection group, and virtual server in your iWS instance.

    • you configure the problem Init function as LateInit in magnus.conf. This is done by adding the LateInit = yes argument to the Init line.

    • you do not dynamically reconfigure the server after it is started.

    If the above conditions are met, the Init function will be executed in an NSAPI context compatible with previous releases of iWS where only a single virtual server exists, and where this problem will not occur.

Problem 540506. TempDir Must be on Local File System.

For the magnus.conf TempDir directive, the TempDir directory must be located on a local file system in order for the server to function correctly. If the TempDir directory is on an NFS mount, the server may fail to function correctly.

Problem 542243. Couldn't Update Latest Data on UI Using IE 5.0.

When using Micosoft's Internet Explorer web browser, version 5.0 is supported for end users only. For administrators, changes to the Sun ONE Web Server Administration Server configuration can be saved only when using Internet Explorer version 5.5.

Problem 544452. A Change Made to Edit Listen Sockets Groups page Does not Allow Another Change to the Edit Listen Sockets Page.

When editing a Connection Group Settings value from the Edit Listen Sockets Groups Page, a server update occurs when the OK button is pressed. Following this, if you go to Edit Listen Sockets page again and change another property, such as the Security value from Off to On, then click OK, an error message may appear that states, `Please refresh your screen, data update by another user.' The Security value has not changed.

Workaround

To change a property on the Edit Listen Sockets page after changing a property on the Edit Listen Sockets Groups page, click the OK button twice to effect the change.

Problem 544504. Load Configuration Files Button Should be Disabled When There are Changes in magnus.conf.

After administrative actions lead to changes in magnus.conf (e.g., enabling Search capabilities), the Load Configuration Files button cannot be used.

Workaround

Use the Apply Changes button to load the changes applied to magnus.conf.

Problem 545420. Add Certificate (or Replace Certificate) Page Help Button is Linked Incorrectly.

After installing a certificate and clicking OK, the Add Certificate page (or Replace Certificate page) appears. Clicking the Help link here takes you to the wrong area: Add Certificate Revocation List Page, instead of Add Other Certificate page.

Problem 545727. Help Button from Compromised Key List (CKL) Page is Linked to Help for Certificate Revocation List (CRL) Page.

From the add CRL/CKL link, you can select the CKL file to display the ADD Compromised Key List page. The Help button on this page is linked to help for the CRL page.

Workaround

Scroll down the help window until you see the help for `Add CRL.'

Problem 560821 (NT only). SSL: ncipher GUI Does Not Show on Admin UI Under Security Section.

This problem shows up inconsistently and will be addressed in a future release.

Java and Java Servlets

Problem 556917. JSP: <jsp:include page="*.html" flush="true" /> Throws Exception If Using With POST Method.

Workaround

POST method is permitted on static content by default.

Problem 555814. Web Deploy GUI: Internal Error When User Re-enters "empty" for URI.

If you have only one web application deployed, and you are trying to edit the URI, the URI cannot be empty.

Problem 548362. JDK1.3.1:jvm12.conf: Server Doesn't Start with Default Min/MaxHeapSize.

Workaround:

Set the minHeapSize to 3.5 M and maxHeapSize to 64M.

Problem 552063. (NT and W2K only) wdeploy: Can't Run wdeploy Command.

Workaround

Ignore the following error message when using the commandline tools wdeploy and HttpServerAdmin: "A nonfatal internal JIT (3.10.107(x)) error 'Relocation error: NULL relocation target' has occurred in: 'org/apache/crimson/parser/Parser2.maybeComment (Z)Z': Interpreting method. Please report this error in detail to:

http://java.sun.com/cgi-bin/bugreport.cgi.

Problem 543913 (Solaris only). JVM Options: Default JVM Options Should Be Optimal.

Workaround:

SP1 will support JDK1.3.1. Use /usr/lib/lwp threads for Java applications on Solaris 8. Most JVM and heap tuning are application specific.

  • For JDK1.2.2_07 use jvm.options = -Xgenconfig:64m,64m to tune heapsize depending on memory availability and application requirements.

  • For JDK1.3.1

    • jvm.option=-XX:MaxNewSize=512m

    jvm.option=-XX:NewSize=512m

You can find more info about the flags and other flags from:

http://java.sun.com/docs/hotspot/VMOptions.html

http://java.sun.com/docs/hotspot/gc/

Some of GC tuning flags are applicable to JDK1.2.2_07 as well.

Problem 547740. JDK1.3.1: Configuring iWS for Debugging Servlets and JSPs.

Workaround:

Please refer to JDK 1.3.1 debugging documentation:

You will need to configure iPlanet Web Server 6.0 SP1 to use JDK instead of JRE before you can debug.

On Unix platforms only, make the following changes to the start-jvm script in the https-admserv directory:

  1. Add ${NSES_JDK}/lib/$arch substituting $arch with the appropriate string corresponding to the machine you are running on, for example sparc for SPARC boxes, to the end of the NSES_JRE_RUNTIME_LIBPATH variable.

  2. Make the following changes have to jvm12.conf:

    1. jvm.enableDebug=1

    2. java.compiler=NONE

    3. jvm.option=-classic

    4. jvm.option=-Xnoagent

    5. jvm.option=-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=<port> where <port> should be replaced by an arbitrary unused port number to which the debugger will connect, such as address=5000

  3. Start the iPlanet Web Server.

  4. Connect to the web server using jdb specifying the port number configured above.

    5. jdb -attach <port>

    for example: jdb -attach 5000

You are now ready to debug your servlet or JSP.

Problem 543980. (Solaris only) Negative jsps/servlets Result in Memory Leaks.

JSP compilation errors, such as incorrect JSP syntax, have resulted in an increase in memory (heap memory) on Solaris.

Workaround

To work around this problem, pre-compile JSPs offline to catch such errors, or remove the offending JSP if the error logs contain compilation error messages for that JSP.

Platform-Specific Information

This section describes platform-specific known problems and workarounds for the following platforms:

Windows

It is recommended that you use the Internet Explorer 5.X browser with Windows 2000 SP2 or later Server Edition.

Corrections to Documentation

Corrections in SP3 Documentation

Problem 4607112. After Cipher Default, SSL2, or SSL3 alg selection, web server won't start.

The "Selecting Ciphers" section of the iPlanet Web Server Administrator's Guide Version 6.0 SP1 omits to mention that irrespective of any changes made to the security settings of the Listen Socket, clicking the Cipher Default link configures the server with default cipher settings.

Problem 4629790. ADM:i18n: Latin1(ISO-8859-1) instance names are not displaying properly on JA-NT.

The Server Identifier used by the Administration Server to identify a server instance must be specified using ASCII and not Latin-1 characters.

Problem 4622241. DOC: admin and iWS do not require the same group.

The user you use to run the Sun ONE Web Server should, but not necessarily must, be in the same group as the user you use to run the Administration Server. The iPlanet Web Server 6.0 Installation and Migration Guide incorrectly specifies this as a mandatory requirement.

Problem 4550934. importCore doesn't migrate Init directives that span lines.

The iPlanet Web Server 6.0 Installation and Migration Guide omits to mention that during migration, multi-line Init directives are compressed to single-line directives in the server-id/config/magnus.conf file

Problem 4535864. Chapter 15 Deploying Web Applications doc error.

In Chapter 15 of the iPlanet Web Server Administrator's Guide Version 6.0 SP1, Step 5 under the section "Deploying Web Applications" should read as follows:

"Enter the absolute path to the directory on the server machine into which the contents of the WAR file will be extracted. If the directory does not exist, one will be created."

In the same chapter, the command parameter incorrectly specified as idirectory should read directory.

Problem 4537301. DOC: Steps for using the Solaris Network Cache and Accelerator fails.

In the iPlanet Web Server 6.0 Performance Tuning, Sizing, and Scaling Guide, the section "Using the Solaris Network Cache and Accelerator" omits to mention that if you are using a version of Solaris that is lower than Solaris 8 Update 5, you would need the following additional patches:

  • The recommended patch cluster for Solaris 8

  • Patch 109472-07

  • Patch 109234-05

Problem 4537391. NSAPI Programmer's Guide net_read documentation error.

The documentation for the net_read function in the iPlanet Web Server 6.0 NSAPI Programmer's Guide should read as follows: "The net_read function returns the number of bytes read, which will not exceed the maximum size, sz. A negative value is returned if an error has occurred."

Problem 4537696. Admin:Global|SNMP MA Community|Help: Wrong Operation Title.

In the online help, operations allowed for the SNMP Master Agent Community should read as follows: "Allow ALL Operations", "Allow GET Operations", and "Allow SET Operations."

Problem 4536922. With IE 5.x, clicking the Help button, in some cases, incorrectly links to the top of the help page.

Problem 4543590. DOC: Errors in Help file on Dynamic config.

The <Limit> directive in the section titled "Example of a .htaccess File" of the iPlanet Web Server Administrator's Guide Version 6.0 SP1 has been incorrectly documented. The text should read <Limit GET POST> instead of <Limit> GET POST, and <Limit PUT DELETE> instead of <Limit> PUT DELETE.

Problem 4651997. Docs imply that Microsoft FrontPage `00/'02 Server Extensions are supported.

The iPlanet Web Server Administrator's Guide Version 6.0 SP1 incorrectly states that the Sun ONE Web Server can be extended to support Microsoft FrontPage webs. Third-party server extensions that extend server-side support for Microsoft FrontPage webs are not supported by Sun ONE Web Server.

Problem 4682979. Cluster Management - Documentation for using variables in file transfer is inadequate.

The "Adding Variables" section in the chapter "Managing Server Clusters" in the iPlanet Web Server Administrator's Guide Version 6.0 SP1 does not adequately describe how variables are transferred within a cluster. The paragraph at the end of the specified section should read as follows:

"The variable must also be added to the server's configuration file you are transferring to the slave. For example, if you are transferring the variable port, the variable should be declared in a server configuration file, say server.xml, as shown below:

<SERVER legacyls="ls1" qosactive="no" qosmetricsinterval="30" qosrecomputeinterval="100">

...

<LS id="ls1" ip="0.0.0.0" port="$port" security="off" acceptorthreads="1" blocking="no">

...

</SERVER>

You can set variables with different values for each slave in the configuration file. Once added, variables can also be edited and deleted using the drop-down Option list in the Add Variables page."

Problem 4687544. Cannot enable remote servlet debugging with JDK 1.3.1.

The instructions for remote servlet debugging as documented in the iPlanet Web Server 6.0 Enterprise Edition Programmer's Guide to Servlets require the use of JDK 1.2.

Problem 4691967. obj.conf mis-spelled as obj.con in the Cluster management help page.

The configuration file obj.conf has been incorrectly spelled as obj.con in the online help page for Cluster Management | Cluster Control.

Corrections in SP2 Documentation

Problem 560092. Correction to NSAPI Programmer's Guide.

By default, the server sends the requested file to the client by calling the send-file function. The directive that sets the default should read:

Service method="(GET|HEAD)" type="*~magnus-internal/*" fn="send-file"

Problem 555648. Core: Restore Configuration Fails to Restore web-apps version .1 and server.xml version.1 file.

Removal of the web-apps.xml column of Restore Configuration page in the Server Manager causes the online help for that page to be inaccurate.

Problem 555725. Changed Web Applications: No Clear Indication If Application is Enabled or Disabled.

A new column for `State' has been added to the `Edit Web Application' page of the Virtual Server Manager, which displays whether the installed application is `Enabled' or `Disabled', depending on the enable value (enable=TRUE/FALSE) in the web application file for that application (URI). This screen change was made after iPlanet Web Server 6.0 SP1, and is not reflected in the Administrator's Guide or online help.

Problem 553736. AcceptLanguage documentation is incorrect.

Corrections in SP1 Documentation

The AIX platform is listed as a supported platform in some documents; however, it is not supported at this time.

Problem 556074. A Bug Against the Programmer's Guide.

The default value for StrictHttpHeaders was changed from `on' to `off' in SP2b.

Problem 551651. A Bug Against the Programmer's Guide to Servlets.

Numerous chapters refer to themselves as "in this appendix."

Problem 555993. Incorrect Parameter Naming in Programmer's Guide to Servlets.

jvm.compiler found twice on page 52 under `Debugging Servlets and JSPs' is not a recognized parameter in VM. jvm.compiler should read java.compiler.

Problem 556431. Duplication of Content in Administrator's Guide.

The steps on page 234 `Configuring the SNMP Master Agent' are a duplication of `Installing the SNMP Master Agent' on page 230, and are inaccurate. The steps should read `Configuring the SNMP Subagent':

  1. From the Administration Server, select the server instance and click Manage.

  2. Select the Monitor tab.

  3. Select SNMP Subagent Configuration.

  4. (Unix only) Enter the name and domain of the server in the Master Host field.

  5. Enter the Description of the server, including operating system information.

  6. Enter the Organization responsible for the server.

  7. Enter the absolute path for the server in the Location field.

  8. Enter the name of the person responsible for the server and the person's contact information in the Contact field.

  9. Select On to Enable the SNMP Statistics Collection.

  10. Click OK.

  11. Click Apply.

  12. Select Apply Changes to restart your server for changes to take effect.

How to Report Problems

If you have problems with Sun ONE Web Server 6.0 SP3 release, contact the following customer support site:

http://www.sun.com/service/support/software/iplanet/index.html

So that customer support can best assist you in resolving problems, please have the following information available:

  • Description of the problem, including 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

For More Information

For more information, refer to the following Internet locations:


Copyright 2002 Sun Microsystems, Inc. All rights reserved.