Release Notes for Sun Java™ System Web Server 6.1 2004Q3 SP3

Release Notes for Sun Java™ System Web Server

Version 6.1 SP3

Part Number 817-7953-05

September 2004

Sun Java™ System Web Server 6.1 2004Q3 SP3 (hereafter referred to as Sun Java System Web Server 6.1 SP3) contains important security vulnerability fixes. All users of Sun Java System Web Server, especially those with sites that utilize Secure Sockets Layer (SSL) version 3 or Transport Security Layer (TLS), are strongly encouraged to install this service pack. This release also provides support for the HP-UX and AIX platforms.

These release notes contain important information available at the time of release of Sun Java System Web Server 6.1 SP3, including information about features and enhancements, known limitations and problems, technical notes, and pointers to additional resources. Review the release notes prior to installing and configuring your software, and then periodically thereafter for the most up-to-date information.

Complete Sun Java System Web Server 6.1 documentation can be found at the following location:
http://docs.sun.com/db/prod/s1websrv#hic

These release notes contain the following sections:

Features and Enhancements

Sun Java System Web Server provides the following features and enhancements:

Java Servlet 2.3 and JavaServer Pages (JSP) 1.2 Support

Sun Java System Web Server includes a Java™ 2 Platform, Enterprise Edition (J2EE™)-compliant implementation of the Java™ Servlet 2.3 and JavaServer Pages™ (JSP™) 1.2 specifications. A J2EE-compliant web container provides the flexibility and reliability needed to design and deploy web applications that comply with Java™ technology standards. Web applications can be deployed on a per virtual server basis.

For information about these technologies, see the following resources:

For information about developing servlets and JSPs in Sun Java System Web Server, see the Sun Java System Web Server 6.1 Programmer’s Guide to Web Applications.

J2SE Platform 1.4.2_04 JDK/JRE Support

Sun Java System Web Server supports Java™ 2 Platform, Standard Edition (J2SE™) 1.4.2_04 and greater (32-bit only; 64-bit is not supported). J2SE software is bundled with the Web Server and installed during installation, if you choose to install it. You can also install your own JDK at a later time, following installation of the Web Server. If you plan to use the Administration server, a JDK must be installed.

HP-UX Platforms

Note that Sun Java System Web Server 6.1 for HP-UX platforms includes JDK 1.4.1.

WebDAV Support

Sun Java System Web Server supports the Web-based Distributed Authoring and Versioning (WebDAV) protocol, which enables collaborative web publishing with the following features:

WebDAV provides integrated support for content metadata, name space management, and overwrite protection. These technologies, combined with the many authoring tools that support WebDAV, provide an ideal development platform for collaborative environments.

NSAPI Filters Support

As of the 6.1 release, Sun Java System Web Server extends the Netscape Server Application Programmer's Interface (NSAPI) to support NSAPI filters.

Filters enable the custom processing of HTTP request and response streams, allowing a function to intercept and potentially modify the content presented to or generated by another function. For example, a plugin could install an NSAPI filter to intercept an XML page generated by another plugin's Server Application Function (SAF), then transform that XML page into an HTML, XHTML, or WAP page appropriate for the client. Alternatively, an NSAPI filter could decompress data received from a client before presenting it to another plugin.

For more information, see the Sun Java System Web Server 6.1 NSAPI Programmer’s Guide.

HTTP Compression Support

Sun Java System Web Server supports content compression, which allows you to increase delivery speed to clients and serve higher content volumes without incurring a corresponding increase in hardware expenses. Content compression reduces content download time, a benefit most apparent to users of dial-up and high-traffic connections.

For more information, see the Sun Java System Web Server 6.1 Administrator’s Guide.

Search Engine Support

Sun Java System Web Server supports a Java-based search engine that provides full-text search indexing and retrieval. The search feature allows users to search documents on the server and display results on a web page. Server administrators create the indexes of documents against which users will search, and can customize the search interface to meet specific needs.

The default URL end-users can use to access search functionality is:

http://<server-instance>:port number/search

Example:

http://plaza:8080/search

When the end-user invokes this URL, the Search page, which is a Java web application, is launched.

For detailed information about conducting basic and advanced searches, including information about keywords and optional query operators, see the online Help provided with the search engine. To access this information, click the Help link on the Search page.

For more information, see the Sun Java System Web Server 6.1 Administrator’s Guide.

Enhanced Security

Sun Java System Web Server allows you to restrict access using flat file authentication. As of the 6.1 release, Sun Java System Web Server now supports the Java Security Manager. The Security Manager is disabled by default when you install the product, which may improve performance significantly for some types of applications. Enabling the Security Manager may improve security by restricting the rights granted to your J2EE web applications. To enable the Security Manager, "uncomment" entries in the server.xml file:

<JVMOPTIONS>-Djava.security.manager</JVMOPTIONS>
<JVMOPTIONS>-Djava.security.policy=instance_dir/config/server.policy</JVMOPTIONS>

where instance_dir is the path to the installation directory of this server instance.

For more information about server.xml, see the Sun Java System Web Server 6.1 Administrator’s Configuration File Reference.

JNDI Support

Sun Java System Web Server supports the Java Naming and Directory Interface™ (JNDI), which provides seamless connectivity to heterogeneous enterprise naming and directory services.

JDBC Support

Sun Java System Web Server provides out-of-the-box, seamless Java™ DataBase Connectivity (JDBC™), and supports a wide range of industry-standard and customized JDBC drivers.

Sun ONE Studio 5 Support

Sun Java System Web Server supports Sun™ ONE Studio 5, Standard Edition. Sun ONE Studio technology is Sun's powerful, extensible, integrated development environment (IDE) for Java technology developers. Sun ONE Studio 5 is based on NetBeans™ software, and integrated with the Sun ONE platform. (Sun Java System Web Server 6.1 and above also supports NetBeans 3.5 and 3.5.1.)

Sun ONE Studio support is available on all platforms supported by Sun Java System Web Server 6.1 SP3. The plugin for the Web Server can be obtained in the following ways:

Please note that the Sun ONE Studio 5 plugin for Sun Java System Web Server 6.1 SP3 works only with a local Web Server (that is, with the IDE and the Web Server on the same machine).

The behavior of the Sun ONE Studio 5 plugin for Sun Java System Web Server is the same as that for Sun™ ONE Application Server 7. For information about using the web application features in Sun ONE Studio 5, see the following tutorial
http://developers.sun.com/prodtech/javatools/jsenterprise/learning/tutorials/cdshop.pdf

Set the Sun Java System Web Server 6.1 SP3 instance as the default, and then take the same actions described in the tutorial.

Also see the following NetBeans tutorial
http://usersguide.netbeans.org/tutorials/webapps/index.html

For more information about Sun ONE Studio 5, visit
http://www.sun.com/software/sundev/jde/

For additional developer resources, see Additional Sun Resources in these release notes.

Using Sun ONE Studio 5 for Debugging

Sun ONE Studio 5 can be used for "remote debugging" if you want to manually attach the IDE to a remote Web Server started in debug mode. The steps are as follows:

  1. Using the Sun Java System Web Server Administration interface, restart the server instance in debug mode (Server Manager > JVM General > Debug Enabled).
  2. Note the JPDA port number.
  3. Start the IDE.
  4. Choose Debug > Start.
  5. Select the dt_socket method, and then enter the remote machine name and the JPDA port number.
  6. At that moment, any breakpoint created in the IDE on servlet source code of a deployed application will be active.

Active Server Pages Support

Sun Java System Web Server 6.1 SP3 supports the Active Server Pages 3.0 specification through Sun™ ONE Active Server Pages version 4.0.1 (formerly Sun Chili!Soft ASP). Sun ONE Active Server Pages adds a secure, enterprise-grade Active Server Pages engine to the Sun Java System Web Server.

Sun Java System Web Server 6.1 SP3 provides support for Sun ONE Active Server Pages 4.0.1 on the following platforms:

A license is not required for Sun ONE Active Server Pages if you are installing to the Sun Java System Web Server. The Sun ONE Active Server Pages installer is available on the Companion CD if you purchased the Sun Java System Web Server Media Kit, or by download from the following location:
http://wwws.sun.com/software/chilisoft/index.html

Please note the following:

For more information about Sun ONE Active Server Pages, visit the URL listed above.

PHP Compatibility

Sun Java System Web Server 6.1 SP3 is compatible with PHP, the versatile and widely-used Open Source web scripting language. PHP runs on all major operating systems.

PHP version 4.3.2 is recommended for use with Sun Java System Web Server 6.1 SP3. For PHP-related installation and configuration information specific to Sun Java System Web Server, see
http://www.php.net/manual/en/install.netscape-enterprise.php

NSS 3.3.10 and NSPR 4.1.6 Support

NSS support in Sun Java System Web Server 6.1 SP3 has been upgraded from 3.3.5 (in version 6.1) to 3.3.10. NSS is a set of libraries designed to support cross-platform development of security-enabled server applications. Sun Java System Web Server 6.1 SP3 also supports NSPR 4.1.6.

Enhanced Hardware Accelerator Encryption Support

Sun Java System Web Server provides hardware accelerator support for Sun™ Crypto Accelerator 4000, a cryptographic accelerator board that enhances the performance of SSL on the Web Server.

Supported Platforms

Sun Java System Web Server 6.1 SP3 can be installed on the Solaris, HP-UX, AIX, Linux, and Windows platforms. The following table summarizes platform support. For more information about installation requirements, see Required Patches in these release notes, and Chapter 2 in the Sun Java System Web Server 6.1 Installation and Migration Guide.

Note: HP-UX 11i is supported only on PA-RISC platforms.

Table 1  Sun Java System Web Server 6.1 SP3 Supported Platforms

Vendor

Architecture

Operating System

Minimum Required Memory

Recommended Memory

Recommended Disk Space

IBM

PowerPC

IBM AIX 5.1, 5.2*

64 MB

192 MB

256 MB

Hewlett-Packard

PA-RISC 2.0

HP-UX 11i

64 MB

192MB

256 MB

Microsoft

Intel x86

Windows 2000 Server SP4
Windows XP
Windows Server 2003, Enterprise Edition

64 MB

192MB

256 MB

Sun

UltraSPARC*

Solaris 8, 9

64 MB

192MB

256 MB

Sun

x86

Solaris 9

64 MB

192MB

256 MB

Sun

x86

and SPARC

Trusted Solaris 8 (Pro Serve Only)**

64 MB

192MB

256 MB

Linux***

RedHat Intel x86

Red Hat Linux Advanced Server 2.1

Kernel 2.4.9-e.3smp
glibc-2.2.4-26
ncurses-4-5.0-5.i386.rpm

You may also create a symbolic link from libncurses5.so to libcurses4.so, although we recommend that you install ncurses4-5.0-5.i386.rpm.

and Red Hat Advanced Server 3.0

64 MB

192MB

256 MB

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

**Sun or iForce partner professional services highly recommended

***Support for the following Linux operating system is now listed as Deprecated and will be removed with the "next" release of the Sun Java System Web Server 6.0 product:

Please take needed action to move or migrate your Web Servers to a supported operating system.

Required Patches

It is recommended that you update your operating system with the latest applicable patches. Required patches are listed by platform.

Solaris Patches

For the Solaris platform, Sun’s recommended patch list can be found at
http://sunsolve.sun.com/pubpatch

Note that patch 108993-22 (SPARC) or 108994-22 (x86) is required on Solaris 8 when Solaris is configured to use LDAP for authentication.

The following patches are required to use Sun Java System Web Server 6.1 SP3.

Solaris 8 (SPARC)

Solaris 9 (SPARC and x86)

HP-UX Patches

The following patches are required to use Sun Java System Web Server 6.1 SP3.

HP-UX 11i

Note: HP-UX 11i is supported only on PA-RISC platforms.

The Java Out-of-Box tool is used to configure the necessary kernel tunable parameters. Use of this tool is the recommended method for modifying kernel values. If necessary, modify the following tunable parameters to reflect a value equal to or greater than the following:

Caution: Modifying the kernel tunable parameters can have adverse impacts on your system. Do not modify the parameters unless you fully understand what you are doing.

AIX Patches

The following patches are required to use Sun Java System Web Server 6.1 SP3.

AIX 5.1

AIX 5.2

If Java web applications are deployed on the Web Server, then per the IBM JDK documentation the following environment variables must be set to the values specified below before the server is started:

The above snippet can be added directly to the Web Server start script.

Installation, Upgrade, and Migration Notes

This section includes notes about installing, upgrading, and migrating your Sun Java System Web Server. For detailed information about these topics, review the information in the Sun Java System Web Server 6.1 Installation and Migration Guide. References to Sun Java System Web Server 6.1 in the guide also apply to Sun Java System Web Server 6.1 SP3. For known issues in this release of Sun Java System Web Server, see Known Issues in these release notes.

Installation

Do not install Web Server into a directory with spaces in the name.  
It is very important to note that the Web Server will not start if it is installed into a directory with spaces in the name, for instance, Program Files. You will not receive an error message about this during installation, but following installation the server will not start.

Web Server cannot be setup on RHLAS 3.0 without compat-libstdc++
Web Server cannot be installed without installing compat-libstdc++.

Upgrade

When you install Sun Java System Web Server 6.1 SP3 over an existing installation of Sun Java System Web Server, the installer automatically detects and carries out the upgrade.

If you have Sun ONE Web Server 6.1 SP1 installed, have the installer for 6.1 SP3 point to the 6.1 SP1 installed location and then upgrade.

If you have the Sun Java Enterprise System 1 installed on your system and you wish to upgrade the Sun ONE Web Server 6.1 that is part of Sun Java Enterprise System 1 to Sun Java System Web Server 6.1 SP3, refer to the following documentation: http://docs.sun.com/source/817-5760/upgrading.html#wp28053

Migration

Direct migration from a version of iPlanet™ Web Server lower than 4.1 to Sun Java System Web Server 6.1 SP3 is not supported. You must first migrate your legacy server to iPlanet Web Server 4.1, and then to Sun Java System Web Server 6.1 SP3.

For detailed migration information, see the Sun Java System Web Server 6.1 Installation and Migration Guide. This guide contains information about migrating from version 4.1 to 6.1 SP3, and from version 6.0 to 6.1 SP3. Again, references to Sun Java System Web Server 6.1 in the guide also apply to Sun Java System Web Server 6.1 SP3.

Product Documentation

Sun Java System Web Server includes a complete set of product documentation, which can be found at the following location:
http://docs.sun.com/db/prod/s1websrv#hic

Sun Java System Web Server manuals are available as online files in PDF and HTML formats. References to Sun Java System Web Server 6.1 in the documentation also apply to Sun Java System Web Server 6.1 SP3. The following table lists the tasks and concepts described in each manual.

Table 2  Sun Java System Web Server Documentation Roadmap

For Information About

See the Following

Late-breaking information about the software and documentation

Release Notes

Getting started with Sun Java System Web Server, including hands-on exercises that introduce server basics and features (recommended for first-time users)

Getting Started Guide

Performing installation and migration tasks:

  • Installing Sun Java System Web Server and its various components, supported platforms, and environments
  • Migrating from a previous version of Sun Java System Web Server

Installation and Migration Guide

The guide can also be accessed from your Web Server installation: server_root/manual/https/ig/

Performing the following administration tasks:

  • Using the Administration and command-line interfaces
  • Configuring server preferences
  • Using server instances
  • Monitoring and logging server activity
  • Using certificates and public key cryptography to secure the server
  • Configuring access control to secure the server
  • Using Java™ 2 Platform, Enterprise Edition (J2EE™ platform) security features
  • Deploying applications
  • Managing virtual servers
  • Defining server workload and sizing the system to meet performance needs
  • Searching the contents and attributes of server documents, and creating a text search interface
  • Configuring the server for content compression
  • Configuring the server for web publishing and content authoring using WebDAV

Administrator’s Guide

The guide can also be accessed from your Web Server installation: server_root/manual/https/ag/

Using programming technologies and APIs to do the following:

  • Extend and modify Sun Java System Web Server
  • Dynamically generate content in response to client requests
  • Modify the content of the server

Programmer’s Guide

Creating custom Netscape Server Application Programmer’s Interface (NSAPI) plugins

NSAPI Programmer’s Guide

Implementing servlets and JavaServer Pages™ (JSP™) technology in Sun Java System Web Server

Programmer’s Guide to Web Applications

Editing configuration files

Administrator’s Configuration File Reference

Tuning Sun Java System Web Server to optimize performance

Performance Tuning, Sizing, and Scaling Guide

Resolved Issues

This section lists the most important issues fixed in the following releases:

Issues Resolved in 6.1 SP3

The following table lists the issues resolved in Sun Java System Web Server 6.1 SP3.

Table 3  Issues Resolved in Sun Java System Web Server 6.1 SP3

Problem ID

Description

4898077

Enable SSL, inconsistent behavior b/w HttpServerAdmin and Web Server console.

6021151

Problem using HttpServerAdmin to create a JNDI resource containing an LDAP DN.

4798461

GUI does not correctly reflect when "Transmit File" is turned off.

4904896

I18N search: sort encoding list of Default Encoding on search admin GUI.

4905412

UI doesn't seem to permit manage users in keyfile db.

4991338

Web Server admin console does not show all the tabs (in Mozilla browser).

5001819

Web Server 6.1 Nova Search Engine sometimes misses to pick up document.

5014693

Java filters, HTTP compression, and SHTML fail to interoperate.

5021077

Encountering java.lang.NullPointerException if you click on OK button without selecting the Directory Server.

5025617

Web Server's JNDI needs to map resource-env-ref's from sun-web.xml.

5042676

Request flow problem with Client tag code=302.

5046634

There is no functionality equivalent to use-responseCT-for-headers in Web Server 6.1.

5056989

Enable prefixing of hostname in session ID.

Note: you can enable prefixing hostname in session ID (as in 6.0SPx) for the webapp by setting the value of the property prefixSessionIDWithHostname under manager-properties to any of the values, yes, true, or on, in the webapp's sun-web.xml.

In the following example, prefixing hostname in session ID is enabled for the web-app by setting the parameter value to true. The sun-web.xml looks like:

<session-config>
<session-manager>
<manager-properties>
<property name="prefixSessionIDWithHostname" value="true"/>
</manager-properties>
</session-manager>
</session-config>

5057749

Web Server 6.1 SP2: Plugin defined in certmap.conf does not load.

6041356

Memory leak when AdminLanguage and/or DefaultLanguage is specified in magnus.conf.

6057426

The load balancer plugin (formerly Resonate plugin), loadbal.so, does not work on SPARC Solaris.

Note that the location of the loadbal.so plugin is: /plugins/loadbal.so

5065017

Servlet session data problem.

5048051

Create collection fails on Linux with RPM install.

5029954

StackSize is ignored when ConnQueueSize/RqThrottle is 0.

5060906

Authorization dialog pops up for an unprotected directory without index file.

5056989

Add hostname in session ID as in 6.0.

4898077

Inconsistent behavior b/w HttpServerAdmin and iWS console.

5013100

Two ports like 2500 and 02500 are added in server.xml as different ports.

5021077

Encountering java.lang.NullPointerException if you click on OK button withot selecting the Directory Server.

4798461

GUI does not correctly reflect when "Transmit File" is turned off.

5042676

Request flow problem with Client tag code=302.

5046634

2 byte character in http header and plugin programs.

You can enable response header encoding at either at the web-app level by setting the value of the configuration parameter use-responseCT-for-headers to any of the values, yes, true, or on, in the webapp's sun-web.xml. In the following example, response header encoding is enabled for the web-app setting the parameter value to true. The sun-web.xml looks like:

<sun-web-app>

<parameter-encoding form-hint-field="j_encoding"/>

<property name="use-responseCT-for-headers" value="true" />

<session-config>

<session-manager/>

</session-config>

<jsp-config/>

</sun-web-app>

Issues Resolved in 6.1 SP2

The following table lists the issues resolved in Sun Java System Web Server 6.1 SP2.

Table 3  Issues Resolved in Sun Java System Web Server 6.1 SP2

Problem ID

Description

4908631

An error message status is returned when user tries to stop the server when it is not running.

4905681

The AsyncDNS setting is ignored in Sun Java System Web Server 6.1 SP1. The Web Server never performs asynchronous DNS lookups.

Note that even when the magnus.conf contains AsyncDNS on, that Asyncronous DNS is still turned off.

4897074

On Linux only: When you create a collection, PDF files will not be indexed and added to the collection.

4943329

IWSSessionManager doesn't work as expected with Web Server 6.1.

4940418

Third-party profiler support for bytecode instrumentation.

4958755

ServletContext.getContext(String) does not return other contexts when called from the root context.

4536102

ADM:i18n: SNMP community name doesn't show up on Solaris Netscape.

4536739

Admin ACL and Superuser AC: Allow only "from host" does not work.

4629796

ADM:i18n: French Thread pool name displaying garbage on JA-NT (IE & Netscape).

4651206

After adding new mime type file, there is no way of verifying addition from the GUI.

4652009

Customized access log file is not reflected in GUI in View Access Log tab.

4664945

Internal Error from URL forwarding form.

4666409

Clearing the ErrorResponse CGI files name.

4676946

No validation of virtual server settings form.

4676950

Internal Error on removing http:// from URL forwarding form.

4676934

dist-admin: Override default ACI in Web Server 6.0 SP2.

4682894

Cluster management - Selection of source server deselects target servers.

4704385

Cluster: Null message in modify cluster when ok is clicked soon after reset.

4705204

Newly added acl files are not getting deleted after selecting delete.

4706063

Chroot and Directory are not validating correctly.

4711353

Admin: Global|SNMP Master Trap Warning displays "Form Element Missing:manager?".

4718914

Turn the security ON for any instance server without installing certificate.

4724503

After enabling IPv6 on UI Edit listen socket, server will not start.

4705181

User and group is not validating for the users and accepting blank spaces in cgi.

4727597

Admin GUI gets cluttered when a new server is added with a duplicate Port.

4732877

Urlhosts field does not accept more that one hostname.

4745314

$id variable in Docroot in a VSCLASS is not working on Windows.

4763653

Validation required for the form elements in document preferences page.

4765709

ADMIN: 'Configure Directory Service' not validating binddn/password.

4764307

Magnus.conf: Performance settings: accepting -ve numbers.

4814097

Unable to select "none" as program item under program groups in GUI.

4862498

New directory Service Screen not connected to interface.

4870613

Back button not working for frames in Netscape 7.

4849907

Shtml is parsed when execute permission is not set and configured.

4894033

dist-admin: Functioning of admin ACL "Allow only from host/ip" is not as per doc.

4899105

The highlighting of the connection value in edit virtual server is not correct.

4905175

WebDAV ACL settings are inherited into new Virtual Servers.

4907288

Cluster Management file transfer not working on Windows.

4909678

Web Server 6.1 Digest authentication is not working for flat files.

4910272

Server should not accept mixed slashes for the doc root while adding a new server.

4911070

Web Server 6.1: Add listen socket protocol family field is missing for IPv6 address.

4911630

Many of the fields in the magnus editor doesn't have validations as they are accepting negative integer values.

4911633

Change Password for the user is not working.

4910266

Web Server 6.1: Creating Digest file users via GUI duplicates users in exponential order.

4913566

The URL Forwarding Editing Page is not consistent.

4911550

Getting ServletException while trying to access the server with additional doc.

4919473

Updating Security Realm properties from Admin GUI not reflected in server.xml.

4925938

Getting Null Pointer exception if user mistakenly edits the VS admin url.

4932995

The leading '/' is being removed when deleting web application through admin GUI.

4941027

Cross site scripting in Sun Web server Webadmin interface.

4946187

dist-admin: "Allow Authenticated Users": after enabling dist-admin, if an ACL is set to allow authenticated users only, the server still allows access to other users in the admin group.

4947005

Add server instance is not working on Solaris x86.

4951982

Invalid error message is displayed while configuring LDAP with wrong credentials.

4953147

Cron-based log rotation fails when admin user is root, and instance is non-root.

Workaround:
Change the user to be same as admin server user in the scheduler.conf file.

4950653

"Null" is displayed for QoS vsclass values.

4962624

Admin: No Validation for protocol value in Edit Listen socket.

4963483

The UI gets cluttered if one tries to create an ACL file path with forward slash.

4964069

The commit.exe utility crashes on Windows platforms.

4961999

After adding a VS, the top frame does not show the VS in the drop down box.

4968422

Showing up invalid ACL file on the browser in the webdav screen.

4973079

The GUI retains dismissed invalid port entries and populates it when servername field validation fails.

4975788

classpath edited using IExplorer is broken; server JVM can't start.

4975798

Can't add path to classpath suffix using web-admin.

4988104

Edit virtual servers page should update the connections value correctly.

4991888

Storing the wrong file name for key file configuration.

4992739

Cannot start webserver instance, after modifying its classpath suffix.

4995489

Solaris x86: distributed admin cannot be enabled.

5002905

Super User Access Control cannot be set even when Distributed Admin is not enabled.

4975782

Can't delete external JNDI reference.

4896881

While untaring the Web Server bits, the ownership and group information is not correct.

4970273

FastCGI beta libraries are in RTM Web Server packages.

4989231

Server fails to start up on Linux platform. Wrong JDK path during build.

4995447

Web Server 6.1 SP2 RHlinux unable to access admin GUI; throws error message after login.

4925475

The server.xml createconsole attribute is ignored.

4536194

CGI subsystem makes blocking calls from NSPR user threads.

4615933

CORE:SHTML: can't set Content-encoding for .shtml files.

4651056

Web Server returns 404 for files starting with "..".

4682434

CGI script fails that grabs environment variables fails to execute.

4684775

Async DNS is disabled by default.

4721021

Unable to access absolute URI on SSL enabled server.

4754934

Vignette NSAPI plugin on Web Server 6.0 not functioning correctly when using HTTP1.1.

4770294

Web Server 6 on Windows should add CR character to the end of line in access log.

4786612

The Web Server treats ':' as a separator between hostname/IP and port in several places. This code needs to be updated to recognize when the ':' is actually part of an IPv6 address.

4787310

Eviction fails in NSFC when SmallFileSpace is set to low value.

4788075

Setting the PATH variable in magnus.conf for Web Server 6.0 SP5 does not work.

4855807

AIX: Web Server hangs after restarted by watchdog.

4873766

upload-file does not work correctly with chunked requests.

4882838

Unable to specify protocol for URL in generated redirects.

The server generates a self-referencing URL whenever it sends a redirect to a client. As of Web Server 6.1 SP1, the servername attribute of the LS element in server.xml can be used to configure the scheme used in server-generated self-referencing URLs.

For example, if an SSL offloader sits between the Internet and the Web Server instance, decrypting SSL-encrypted traffic for www.sun.com and relaying it to the Web Server on port 8080, an LS element such as the following could appear in server.xml:

The "https://" prefix in the servername value instructs the server to use the https scheme in self-referencing URLs even though the LS is not configured to handle SSL traffic.

4889081

Internal log rota creates empty logs.

4916331

Keep-alive connections can hang under light load.

4929848

Performance: Web Server polls kstat once per second.

4933483

SIGCHLD signals are reported on startup.

4935582

TCP_NODELAY need not be set for AF_NCA.

4930642

Source returned when the file's mime.types entry does not end with a carriage return.

4941741

Web Server 6.1 SP1 server on Solaris 8 SPARC fails to start due to libCld.so.

4945994

fc_net_write should result in a single system call.

4951860

httpagt depends on NETSITE_ROOT variable.

4957158

fc_open fails when running specweb99 on x86 build.

4958571

PR_NetAddrToString performance is less than expected.

4961864

Web Server hangs when using rotate-callback.

4969637

Minor coding error in send-error SAF.

4976490

Log messages truncated.

4975675

Dynamic reconfiguration fails when server is under load.

4976910

NSFC_GetEntryPrivateData() calls NSFC_ExitCacheMonitor() when no entry exists.

4986700

Last-modified and Etag are suppressed when Servlet filters are used.

5012107

POST request body consumed twice when using bad plugin.

4651207

On Document preference web page, file to use for error responses needs to be provided.

4727444

Access Log reports incorrect data.

4753601

MaxRqHeader directive in magnus.conf is not working as desired.

4903449

Performance affected with multi-process mode and one thread.

4913289

Help on "Edit Virual Class" doesn't give complete criteria for VS class deletion.

4935797

certmap.conf file location mis-represented.

4940040

Administrator's Configuration File Reference defines nonexistent TYPE element.

4942750

Search example is incorrect.

4943631

Wrong documentation on Thread pool config file.

4912254

WebServer installation failed due to 'set -o noclobber' in .env.

4970188

Rpm can't locate system umask.

4971298

pkgchk -n fails for Webserver package in JES.

4962059

Admin passwd stored as plain text in file setup.inf.

4858152

Access log entries in server.xml of the migrated instance points to invalid path.

4904088

Migration final page needs to html encode the "<" and ">" characters.

4935420

Resource picker for restrict access fails for migrated instance of 6.1.

4944850

Address directive not properly migrated when migrating from Web Server 4.1 to 6.1.

4946829

Admin: creating new vs after migration causes $user: unable to find value.

4986761

Web Server 6.0 migration fails.

4869527

SNMP: protos test no. 3 fails for RH Linux 6.2/7.2/Adv Server 2.1 & Sun Linux 5.

4948397

Web Server 6.1 SP1 SNMP is not working.

4976953

AIX 6.0 SP6: forbidden error to a GET for a file with correct group permissions.

4800173

Performance issue with large ACL file in conjunction with many Virtual Servers.

4822720

Keep-alive subsystem should be dynamically tuned.

The keep-alive subsystem requires tuning for optimal performance. In Web Server 6.0, this subsystem was tuned for heavy load and performs poorly when there are only a handful of concurrent keep-alive connections. The keep-alive subsystem was modified for Web Server 6.1 SP2 so it performs some dynamic tuning to accomodate the actual load.

4910869

NSFC enhancement needed.

Add the ReplaceFiles nsfc.conf directive.

When ReplaceFiles=true (default), the existing file cache behaviour is preserved.

ReplaceFiles=false indicates that once a file is cached, its file cache entry should never be discarded to make room for another file; this is useful in benchmark scenarios because it allows us to eliminate contention on the hit list lock.

4966497

Perf Dump data for Average Queueing Delay is not correct.

4908986

Jdbc: blob sample: Servlet code UploadServlet mishandles SQL exceptions.

4913228

Missing quote in oracle script for jdbcRealm sample application.

4970955

Cross-site security issue with Apache sample(\plugins\java\samples\webapps\simple).

4972573

Incorrect behaviour in Webapps-Simple sample application in Web Server 6.1 SP1.

4972587

Incorrect instructions in index.html of i18n Sample Application.

4976454

Samples shipped with Web Server 6.1.

4991775

Validation of cookie name in cookie example servlet.

4904896

i18n search: sort encoding list of Default Encoding on search admin gui.

4908010

Unable to remove search collection for a newly created VS before doing an apply.

4908401

i18n: unlocalized timestamp for each search returned documents.

4903319

Does not add a JSP file to the collection.

4910222

Error on Windows when trying to create a collection with a docroot with backslashes.

Workaround:
 This behavior occurs when you specify a docroot that has backslashes or mixed slashes. Use forward slashes.

4911548

Server returns ConfigException while creating the duplicate search collection.

4911656

I18N: Can not go to "sort by date" link while searching multibyte characters.

4913909

i18n: error adding file with Korean filename - skipping since no read permission.

4926414

i18n-ko: reindexing collection hangs when missing 1 or more existing docs.

4947065

The search webapp shows only a maximum of 11 collections.

4947624

Ineffective alert message displayed while Reindexing On Windows.

4950552

Wrong no of results for particular output results (11, 21, 31...).

4956415

Web Server 6.1 Search: requesting an ability to display the meta tag description.

4950644

Ineffective alert message displayed while creating a duplicate collection on Lin.

4962659

Search criteria is getting truncated to 100 characters.

4967580

Search displays wrong hyperlinks for the SSL enabled instance.

4970181

Stellent filters need to be added to the Linux and Solaris x86 builds.

4975327

indexMetatags of the nova search should be set automatically.

4975367

Indexing for the meta tag should be case-insensitive.

4997149

Remove documents with *.* pattern is not removing all the files when the excludeExtensions property is set.

4997178

Server returns null pointer exception while indexing .sxg file when excludeExtensions is set.

4997697

Page numbers are not displayed properly on the search results page.

4749239

ACLI: Incorrect processing of ACL.

4844616

dbswitch misconfiguration causes crash.

4854698

Plugin crashes with malformed request.

4866965

ACLI: Failed authentication will be logged twice in the server errors log file.

4880864

ACL: Web Server returns 404 Not found errors when ACLs deny access.

4915326

WEBC: granting signedBy permissions to jar files does not work.

4808402

Native authenticator support.

4934083

LDAP: Crash during LDAP authentication.

4934562

webc: getRemoteUser() does not work for standalone jsps.

4935669

webc: request may not always contain client cert data.

4935570

Cert data not always present even when available.

4946762

Out of box default realm should be native.

4948123

Web Server 6.1 incorrectly reports client key size in certain situations.

4932547

Tomcat AuthenticatorBase returning 500 instead of 403.

4949842

webc: isUserInRole() will not match when using core authentication.

4957829

LDAP: user can enter wildcard '*' for UID in basic authentication.

4960013

Cannot have more than one ldap realm.

4968857

htconvert not converting .nsconfig wildcard patterns correctly.

4976277

Using jdk 1.4.1 provided jndi connection pool for ldap pooling.

4997838

Webserver does not start on RHL AS 3.0 with Security turned On.

5003531

500 error when accessing web app with transport-guarantee=CONFIDENTIAL in non-SS.

5004542

ASN.1 parsing bugs / brute forcer program can cause Web Server crash.

5016494

NSS: Crash in DER_UTCTimeToTime with corrupt certificate.

4996219

Webservd leaks memory on RedHat Linux Advance Server 3.0.

4954789

Web Server deployment fails with ClassCastException.

4968882

htconvert does not work on 6.1 style server.xml.

4909378

Help Button for edit webdav is not pointing to the correct help page.

4657465

Need to disable cookie-encoding.

By default, the Sun Java System Web Server URL encodes the cookies before sending them to the client. If you do not want the cookies to be encoded, add the following line to sun-web.xml:

<property name="encodeCookies" value="false"/>

For the above example, put the line directly under the tag; do not embed them in any other tag.

4707989

WEB-APP/JSP: load-on-startup not working on JSP files.

4918754

Web Server 6.1 cannot process HTTP URL GET parameter that is in 8-bit charset.

4924921

Cannot set 800 MB of jvm max heap size on Win2k using JDK 1.3.1.

4926336

Using % in the value of jsp:param corrupts the query string.

4927770

Server aborts with SIGABRT from within libjvm.

4928358

JSP errors are wrongly reported as Not Found errors.

4930374

extra-class-path attribute in class-loader element in sun-web.xml doesn't work as expected.

4932893

Dynamic reloading doesn't work for web application descriptor files (eg. web.xml.

4939370

Web container thread names are not unique.

4960873

NPE encountered when a session is expired simultaneously by two (2) threads.

4973927

EPIPE signal not caught as an IOException from OutputStream.write().

4983707

Changing the log level to Security causes NullPointerException upon st.

4981028

"distributable" semantics in web.xml is not honoured by the web container.

4993468

getResourcePaths returns paths that contain "//".

4997593

Poor integration between NSAPI srvhdrs and HttpServletResponse headers.

4930327

Destination headers are not URL decoded in MOVE/COPY requests.

4930329

Default values of maxpropdepth is poorly chosen.

4952492

MOVE method should "rename" files when possible.

4997756

LOCK-UNLOCK is not working properly and UI does not show up lock info properly.

4761188

LDAP: Improve LDAP dynamic group performance for ACI's.

For performance reason, a new ldap config parameter, "dyngroups fast" is introduced for SP2. With this config, Web Server will make assertion about group memebership bypassing nested individuals among dynamic groups.

For example, assuming that user "alpha" belongs to group "a", group "a" is a member of group "b" by group "b" memberURL definition (dynamic group), and your acl only grants group "b" access. In such case, Web Server will deny access from "alpha" because "alpha" is not regarded as memeber of group "b".

If you want to support nested group in such case, don't define this new config for ldap authentication service. (and you won't get performance gain consequently.) Sample config: directory ldapregular ldap://localhost:389/o=TestCentral
ldapregular: dyngroups fast

4940418

3rd party profiler support for bytecode instrumentation.

4943329

IWSSessionManager doesn't work as expected with Web Server 6.1.

4951264

Server crash during Java-triggered reconfiguration and server shutdown.

4958755

ServletContext.getContext(String) does not return other contexts when called from root context. It simply returns the root context.

Issues Resolved in 6.1 SP1

The following table lists the issues resolved in Sun Java System Web Server 6.1 SP1.

Table 4  Issues Resolved in Sun Java System Web Server 6.1 SP1

Problem ID

Description

4642650

Option needed to disable appending of absolute URL in servlet/JSP container.

Fix details
New property added to sun-web.xml: relativeRedirectAllowed
Default value: false
Description: If true, allows the web application to send a relative URL to the client using the HttpServletResponse.sendRedirect() API (that is, it suppresses the container from translating a relative URL to a fully qualified URL).

4793938

Enabling Remote File Manipulation from the Server Manager UI allows any remote user to obtain a listing of any directory in the server's URI space.

4904201

javahome path wrongly set when adding a server with no bundled JDK.

4911580

Adding a new server instance may fail with a Server Error message.

4928794

Server restarts when trying to create null resource by PUT.

4929913

Search engine does not extract and index FTS information from PDF files.

Fix details
This fix applies to all supported platforms except Linux.

The Author, Subject, and Keywords metatags are always indexed. Functionality has been added that now allows arbitrary metatags to be indexed, including those produced when converting the FTS_* attributes from PDF files. Manual configuration of a new setting in server.xml is required, as described below.

  • In the SEARCH section of server.xml, add a PROPERTY with name="indexMetatags". The value should be a comma-delimited list of metatag names (note that the Author, Subject, and Keywords metatags are always indexed, regardless of this setting).
  • To index the metatags resulting from the conversion of PDFs and other types of documents, this configuration must use the name of the metatag, rather than the name of the “field” in the particular document type. For example, to index the FTS_Title contents from PDF files, "Title" must be a component of the "indexMetatags" setting:

    <PROPERTY name="indexMetatags" value="Title"/>

Note: See issue 4956415 in the Search section for details about displaying custom metatag information in search results.

4933935

On Solaris 9: Reconfig does not work in package-based installs.

4945089

ASN.1 parsing issue in SSL.

A problem has been identified in the implementation of the SSL protocols used by the Web Server that may be exploited as a Denial of Service attack. Sun Java System Web Server 6.1 SP1 fixes this problem. If you use the Web Server to host sites that utilize SSL version 3 or TLS, you are strongly encouraged to install this service pack.

4950388

The “reconfig” command does not work on Windows XP.

4964069

The commit.exe utility crashes on Windows platforms.

Issues Resolved in 6.1

The following table lists the issues resolved in Sun Java System Web Server 6.1.

Table 5  Issues Resolved in Sun Java System Web Server 6.1

Problem ID

Description

4540254

Rotating log files shouldn't require server restart on UNIX.

4727146

Logs filling with "connection reset" entries.

4786735

Installer doesn't set proper JDK CLASSPATH/LIBPATH when the external JDK is used.

4792721

Incorrect error messages when LDAP server is offline.

4799452

sun.tools.javac.Main has been deprecated, exception stops valid JSPs.

4801874

ACL_LDAPSessionAllocate always returns LAS_EVAL_FAIL.

4811418

Digest authentication crashes.

4819405

Memory growth/leak of slapd process with digestauth plugin.

4820513

digestauth plugin code is not thread safe.

4839875

When using cachefs/nfs as ClassCache and document-root, Sun Java System Web Server doesn’t always pick up the new JSP.

4842190

Web Server crashes when receiving Accept-Language header larger than 15 languages.

4842574

Server crash with malformed request.

4842601

Accept-Language header security issue.

4846832

CRL corrupts database.

4848896

digestauth plugin crashes for a particular type of request.

4849914

Memory leak in digestauth plugin for a particular type of request.

4855546

Log analyser vulnerability.

4858026

JSP: crash in getParameter when posting large amounts of data.

4867887

Basic auth fails for users with uids that have spaces.

4903319

When you create a collection, not all documents will be indexed and added to the collection.

Known Issues

This section lists the more important known issues and limitations at the time of the Sun Java System Web Server 6.1 SP3 release. The issues are listed by category:

General

The following table lists general known issues.

Table 6  General Known Issues

Problem ID

Description

4991487

SEC_ERROR_BAD_DATABASE errors

Errors are logged from NSS after the DBM's in-memory cache reaches the maximum allowable size. When this behavior happens, DBM will try and create temporary files in order to expand its memory space. If it fails to create temporary files, it starts logging the following errors:

[11/Dec/2003:10:52:54] failure (20073): Error receiving connection (SEC_ERROR_BAD_DATABASE - Problem using certificate or key database)
[11/Dec/2003:10:52:54] failure (20073): Error receiving connection (SEC_ERROR_BAD_DATABASE - Problem using certificate or key database)
[11/Dec/2003:10:52:54] failure (20073): Error receiving connection (SEC_ERROR_BAD_DATABASE - Problem using certificate or key database)

This in turn results in the SEC_ERROR_BAD_DATABASE errors.

Workaround:
Set $TMP in the start script of web server to point to a file system (dir) writable by webserver user.

6021151

Problem using HttpServerAdmin to create a JNDI resource containing an LDAP DN containing commas.

When using the cmd line utility HttpServerAdmin in //bin/https/bin to specify an external JNDI resource it is not possible to correctly configure the URL for an LDAP provider if the DN contains commas (a standard requirement). The commas are acting as the delimiter between properties and therefore the resulting server.xml contains more properties than expected. This would be in keeping with the HttpServerAdmin help page description obtained by executing with the -h argument.

Workaround:
For HttpServerAdmin, to escape the ',' in the property use '\\' as the escape character. Alternatively you can specify the value containing the commas in the DN for the java.naming.provider.url property via the WS Admin GUI, or manually edit the server.xml file.

Administration

The following table lists the known issues in Administration.

Table 7  Known Issues in Administration

Problem ID

Description

5048940

Superuser Access Control page in Admin UI not accessible after upgrade from SP1.

Workaround:
This problem will still surface when the upgrade path is from 61sp1-> 61sp2 -> 61sp3. (This bug will not show up in case of direct upgrade to 61sp3; that is, 61sp1->61sp3 or 61sp2->61sp3). The following workaround can be applied to addrress the issue:

When the Super-user access control page is not accessible, edit the obj.conf:
1. Add the directive:
AuthTrans fn="admin-check-admpw" admpwfile="/<SERVER_ROOT>/https-admserv/config/admpw" admdns="*" admip="*" final=true

2. Next, delete the directive:
PathCheck fn="admin-check-admpw" admpwfile="/<SERVER_ROOT>/https-admserv/config/admpw" admdns="*" admip="*" final=true

When the Distributed admin page is not accessible, edit the obj.conf:
1. Add the directive:
AuthTrans fn="admin-check-admpw" admpwfile="/<SERVER_ROOT>/https-admserv/config/admpw" admdns="*" admip="*" final=false

2. Next, delete the directive:
PathCheck fn="admin-check-admpw" admpwfile="/<SERVER_ROOT>/https-admserv/config/admpw" admdns="*" admip="*" final=false

6021151

Problem using HttpServerAdmin to create a JNDI resource containing an LDAP DN containing commas.

Workaround:
For HttpServerAdmin to escape the ',' in the property use '\\' as escape character (and use '\' in Windows platforms).

In the property java.naming.provider.url=ldap://localhost:389/ou=loggingQueues,ou=tms,ou=services,ou=abc the ',' are escaped as shown here:
-property java.naming.provider.url=ldap://localhost:389/ou=loggingQueues\\,ou=tms\\,ou=services\\,ou=abc

5007892

dist-admin: ACL deletion does not clean up obj.

Workarond:
Comment out the NameTrans for https-admserv:

#NameTrans fn="assign-name" name="https-admserv" from="/https-admserv/*"

5035129

Unable to manage DS user/group/ou using WS 6.1 SP2 Admin on RHLAS 3.0 only.

4650456

View Access and View Error doesn’t work properly with multibyte characters.

4652585

When distributed admin is enabled, the local admin user becomes disabled

Workaround
Create a user with the default admin user name within the distributed admin group.

Note that the newly created LDAP admin user must have the same password as the Web Server admin user.

4725683

The log file date stamp does not take the local time zone into account, and shows the incorrect date.

Workaround
If the date in the log file filename extension should match the date of the log entries themselves, configure the server to rotate the log files at 23:59, the end of the day.

4761960

In Version 6.0SP4, cannot enable distributed admin when using SASL and anonymous bind.

Workaround
Do not use anonymous bind to SSL enabled directory server.

4841310

Can't get REMOTE_USER variable when authenticated by .htaccess.

Workaround
If you enable .htaccess files, the server checks for .htaccess files before serving resources. The server looks for .htaccess files in the same directory as the resource and in that directory's parent directories, up to and including the document root. For example, if the Primary Document Directory is set to /sun/server/docs and a client requests /sun/server/docs/reports/index.html, the server will check for .htaccess files at /sun/server/docs/reports/.htaccess and /sun/server/docs/.htaccess.

Note that the server's Additional Document Directories and CGI Directory functionality allows an administrator to define alternate document roots. The existence of alternate document roots affects .htaccess file processing. For example, consider a server with the Primary Document Directory set to /sun/server/docs and a CGI program at /sun/server/docs/cgi-bin/program.cgi. If you enable CGI as a File Type, the server will evaluate the contents of both /sun/server/docs/.htaccess and /sun/server/docs/cgi-bin/.htaccess when a client issues a request for the CGI program. However, if you instead configure a CGI Directory at /sun/server/docs/cgi-bin, the server will inspect /sun/server/docs/cgi-bin/.htaccess but not /sun/server/docs/.htaccess. This occurs because specifying /sun/server/docs/cgi-bin as a CGI Directory marks it as an alternate document root.

4865295

The End User Administration feature (under Distributed Administration in the Administration interface) is no longer supported.

4882999

Inconsistent look and feel to the pages in the Administration UI.

4888696

The Add Server page in the Administration UI "disappears" in Netscape 7.0 when insufficient information is entered.

Workaround
Enter complete information on the Add Server page before clicking OK. If necessary, reload the page to restore the Add Server UI, or click another page or another tab and then navigate back to the Add Server page. This problem occurs only in Netscape 7.0.

4910309

The word "null" is incorrectly displayed on an alert message.

This displays when editing directory services in the Pick Directory for Virtual Server page in the Virtual Server Manager.

4905808

Superusers cannot access the Administration interface after enabling distributed administration.

Workaround
After enabling distributed administration, create a user in LDAP with the same administration user name and password as that of "superuser."

4908694

Default link not working for logging settings.

The Default link on the Logging Settings for Virtual Server page does not set the default path, but rather acts as a reset button.

4910197

When editing a JDBC resource, the properties page retains values after they’ve been deleted.

4911552

.shtml files are parsed when they shouldn’t be.

This issue pertains to the Parse HTML page on the Content Management tab in the Class Manager. The .shtml files will be parsed even when settings on this page are configured so that they shouldn’t be. For example, if you specify just "Yes, with exec tag" and "All HTML files," .shtml files will still also be parsed.

No ID

The sun-web.xml file bundled with the Web Server points to the wrong DTD location.

The correct location is:
http://www.sun.com/software/dtd/webserver/sun-web-app_2_3-1.dtd

Cohabitation

The following table lists the known issues in Cohabitation.

Table 8  Known Issues in Cohabitation

Problem ID

Description

4869693

On Windows, the Web Server installation overwrites Sun™ ONE Directory Server .dll files due to cohabitation issues with Directory Server 5.x.

Core

The following table lists the known issues in Core.

Table 9  Known Issues in Core

Problem ID

Description

4939491

On HP-UX: Executing the ./stop script gives an error message and kills the process group.

Documentation and Online Help

The following table lists the known issues in Documentation and Online Help.

Table 10  Known Issues in Documentation

Problem ID

Description

4898077

Enable SSL, inconsistent behavior b/w HttpServerAdmin and iWS console.

5056989

The following tables in Sun ONE Web Server 6.1 Programmers guide to Web Applications should be updated with new property information (for reference, see bug #5056989 in Resolved Issues for SP3).

Sun ONE Web Server 6.1 Programmer's Guide to Web Applications -> Session Managers

  • Table 4-4 manager-properties Properties for StandardManager
  • Table 4-5 manager-properties Properties for PersistentManager
  • Table 4-6 manager-properties Properties for IWSSessionManager

Sun ONE Web Server 6.1 Programmer's Guide to Web Applications -> Deploying Web Applications -> Elements in the sun-web.xml File

  • Table 6-15 manager-properties Properties

All the 4 tables mentioned above should be updated with new property "prefixSessionIDWithHostName".

The values for this new property are as follows:

  • Property Name: prefixSessionIDWithHostname
  • Default Value: false
  • Description: Tells the session manager to enable prefixing hostname in session ID (as in 6.0SPx) for the webapp. When this value is 'false', which is by default, the session IDs are not prefixed with hostname.

4849907

Online Help shtml admin page should display the following information:

Files with the execute bit and the extension .html or .htm instead of Files with the execute bit and the extension .shtml.

4684775

Async DNS is disabled by default: Additional info required for Administrators Configuration File Reference .

AsyncDNS is not supported on Windows.

There are three (3) sections of the Administrators Configuration File Reference that require an update. The content enclosed within paranthesis should read "Specifies whether Asynchronous DNS is allowed" First, in the DNS Lookup - AsyncDNS section:

Specifies whether asynchronous DNS is allowed. (This directive is ignored. Even if the value is set to on, the server does not perform asynchronous DNS lookups.)

In Appendix A: Configuration Changes Between iPlanet Web Server 4.1 and Sun ONE Web Server 6.1 (Table A-1):

AsyncDNS AsyncDNS (Ignored. Even if the value is set to on, the server does not perform asynchronous DNS lookup.)

In Appendix A: Configuration Changes Between iPlanet Web Server 6.0 and Sun ONE Web Server 6.1 (Table B-2):

AsyncDNS AsyncDNS (Ignored. Even if the value is set to on, the server does not perform asynchronous DNS lookup.)

5019026

Localization Issue: Many second level online help screens display in English only.

A number of files in manual/https/ag/ are not localized as localized online help files refer to these files internally.

4657465

encodeCookies property Web App Programmer's Guide

By default, the Sun ONE Web Server URL encodes the cookies before sending them to the client. If you do not want the cookies to be encoded, add the following to sun-web.xml:

<property name="encodeCookies" value="false"/>

For the above example, add the line directly under the tag; do not embed it in any other tag. The default value for this flag is 'true'.

5029460

Error in certmap.conf description in Administrator's Guide.

The description of certmap.conf in the Administrator's Guide contains the following text:

The first line specifies a name for the entry and the attributes that form the distinguished name found in the CA certificate. The name is arbitrary; you can define it to be whatever you want. However, issuerDN must exactly match the issuer DN of the CA who issued the client certificate. For example, the following two issuerDN lines differ only in the spaces separating the attributes, but the server treats these two entries as different:

certmap sun1 ou=Sun Certificate Authority,o=Sun, c=US
certmap sun2 ou=Sun Certificate Authority,o=Sun, c=US

Note that the two DNs are identical. The two lines should be changed to read as follows:

certmap sun1 ou=Sun Certificate Authority,o=Sun, c=US
certmap sun2 ou=Sun Certificate Authority, o=Sun, c=US

5031366

Invalid links in the online version of Administrator's Guide.

Sun documentation site hyperlink is not working. There is an extra space in the url. Correct link is: http://www.sun.com

4909738

Documentation error.

In Magnus Editor, LogVerbose and LogVsId are ignored when set to "On" (in lieu of the loglevel and logvsid attributes of the LOG element in the server.xml file).

4911551

Online Help missing documentation of default styles (Styles tab in the Class Manager).

Sun Java System Web Server includes the default styles listed below. These are default objects created in the obj.conf file. Once you begin customizing your server’s configuration, the styles list will change (new ones will be added, others will be removed, and so on). The default styles are as follows:

  • j2ee. Object that invokes the Java environment.
  • es-internal. Object that determines how requests handled by server core are processed.
  • send-compressed. Object that determines how (or if) the server will send precompressed content if it exists on disk (for instance, index.html.gz instead of index.html).
  • compress-on-demand. Object that determines how (or if) the server will compress content on demand.
  • dav. Object that controls how WebDAV requests are processed.

See issue 4911550 in the Administration section in these release notes for an issue related to the default styles.

Installation

The following table lists the known issues in Installation.

Table 11  Known Issues in Installation

Problem ID

Description

5020317

JDK only upgrade results in disabling search (user receives an exception, and search page will not be accessible from GUI).

Workaround
 This exception does not happen if 61sp2 core is also installed along with, or prior to installing JDK alone. In addition, if 61sp2 core is installed on top of a JDK-upgraded Web Server 6.1 SP1, the exception does not show up.

4855263

Sun Java System Web Server will not start if it is installed into a directory with spaces in the name, for instance, Program Files. You will not receive an error message about this during installation, but following installation the server will not start.

Workaround
Do no install the Web Server into a directory with spaces in the name.

4869238

On Windows, the Sun Java System Web Server installer will not take a long name as server_root.

Workaround
Specify a path name for the Sun Java System Web Server installation directory that is no longer than 128 characters (even though the dialog allows you to enter up to 256 characters).

4901205

On Solaris, Control+b does not work on screens that follow the Fully Qualified Domain Name screen in the installer (starting with the User and Group Name screen).

Workaround
If you need to return to previous screens during the installation, quit the installer and start again.

4937915

On AIX: Ctrl-c makes the terminal screen hang during installation.

This occurs on the computer name screen (the screen used to specify the name of the computer on which the Web Server will be installed).

4960048

Some SNMP-related files are overwritten when upgrading to Sun Java System Web Server 6.1 SP1.

Workaround
Back up the following files before the upgrade:

$server-root/plugins/snmp/magt/CONFIG
$server-root/plugins/snmp/sagt/CONFIG

Migration

The following table lists the known issues in Migration.

Table 12  Known Issues in Migration

Problem ID

Description

5007081

Web-apps file status ignored during migration from 6.0 to 6.1

Web-apps status defined at the file level in the server.xml file is not getting migrated. If a user has switched off the status of the web-apps file to supress them, upon migration these apps are exposed.

Workaround:
Edit the server.xml file of the migrated instance and turn off status for each web-app.

4988156

Installation of sp_2 patch on existing install (update)

If you have the Sun Java Enterprise System 1 installed on your system and you wish to upgrade the Sun ONE Web Server 6.1 that is part of Sun Java Enterprise System 1 to Sun Java System Web Server 6.1 SP2, you must use the Java Enterprise System (JES) installer to perform the upgrade. Do not use the separate component installer included with Sun Java System Web Server 6.1 SP2.

Samples

The following table lists the known issues in the sample applications. Note that none of these issues prevent the sample applications from functioning correctly.

Table 13  Known Issues in Samples

Problem ID

Description

5014039

Simple JSPs throw exception due to tag in web.xml

Workaround:
Remove the tag from the web.xml under the simple/src directory. Redeploy the webapp.

No ID

rmi-iiop sample is missing a step.

In the "Deploying the Sample Application" section, after executing the command “ant deploy“ (step 2), restart the web server instance.

Note: Ant is a Java-based build tool and must be downloaded from Apache at http://ant.apache.org. Also see the information provided in <install_root>/plugins/java/samples/docs/ant.html.

No ID

jdbcrealm sample has the wrong Oracle driver name.

In the "Compiling and Assembling the Sample Application" section, step 2b, change the following line from this:

<PROPERTY name="dbdrivername" value="oracle.jdbc.pool.OracleDataSource"/>

To this:

<PROPERTY name="dbdrivername" value="oracle.jdbc.driver.OracleDriver"/>

Search

The following table lists the known issues in Search.

Table 14  Known Issues in Search

Problem ID

Description

4977315
5038203

AIX-Search Engine of 6.1 should have the ability to change the sort order.

Workaround
 For changing default order add '+" as a first character of the sort string. Since '+' in uri is escaped use '%2B' to change the order. In this case change the url to: http://host/search/index.jsp?si=1&ns=10&c=test&qt=*&sb=%2Bwriter.

4684124

If the docroot of an already indexed collection is changed, the document returned by the search throws a ‘Document Not Found’ error.

Workaround
Rebuild the entire collection.

To do so:

  • Remove all documents and add them back again.
    Or
  • Delete the collection and create it again.

4910410

Collection creation may fail in certain cases when a multi-byte label and/or description is specified.

Workaround
Create the collection without specifying the label and description (which are optional), and then set these using the Configure Collection page on the Search tab.

4911725

Search doesn’t work when you search for a word using a different case pattern.

Search results will not be displayed on the search page if you search using a word of mixed case (for example, typing jaVa instead of java or JAVA).

4955069

On HP-UX: i18n — Multibyte Display Name and Description not displayed properly.

Workaround
Set the Display Name and Description from the Configure Collection page after the collection has been created.

4963236

On HP-UX: PDF files are not converted to HTML for inclusion in search collections.

This occurs if the following patch is installed on the HP-UX 11i system:
PHSS_28871 — ld/linker cumulative patch

4974124

On AIX: Can’t create a collection when multibyte Display Name and Description are provided.

Workaround
This problem occurs when the Web Server is started in the zh_CN locale. It does not occur when all locales are installed, or when the server is started in the ‘C’ locale.

Security

The following table lists the known issues in Security.

Table 15  Known Issues in Security

Problem ID

Description

4898077

Enable SSL, inconsistent behavior b/w HttpServerAdmin and iWS console.

Workaround:
Use the folloiwng Syntax:
HttpServerAdmin create -l -id <id> -ip <ip> -port <port> -sname serverName -defaultvs <defaultvs> [-cert <certificate name>] [-sec <on|off>] [-acct <#accthreads>] -d server_root -sinst http_instance

Note: Do not use "true|false" or "1|0" or "yes|no" for the -sec option, use "on|off" instead.

4671445

Sun Java System Web Server cannot connect to an LDAP server over SSL if LDAP client authentication is required.

If Sun Java System Web Server contacts an LDAP server that requires client authentication (in this case, the Web Server is the client), the Web Server’s certificate cannot be sent and access will fail.

4863599

Cannot use the same group name under different organizational units.

If the same group name is used, and you try to restrict access with the group name, Sun Java System Web Server returns an error when clients try to access the site.

Workaround
Use a different group name for each organizational unit.

4963468

In some circumstances, the “list” right has no effect on directory listing.

According to “Setting Access Rights” in Chapter 9 of the Sun Java System Web Server 6.1 Administrator’s Guide, the “list” right is required to obtain directory listings from directories that do not contain an index file. However, in certain circumstances it is possible to obtain a directory listing, even if the applicable ACLs deny the list right. For this reason, if you need to restrict directory indexing, it is recommended that you do so by disabling indexing, as discussed in “Selecting Directory Indexing” in Chapter 16 of the Sun Java System Web Server 6.1 Administrator’s Guide, instead of (or in addition to) denying the list right.

Tools

The following table lists the known issues in Tools.

Table 16  Known Issues in Tools

Problem ID

Description

4905696

On Windows, two WAR files in the Servlet TCK fail to deploy due to an issue with the wdeploy utility. The files are:
servlet_jsh_HttpServletResponseWrapper_web.war
servlet_jsh_HttpServletRequestWrapper_web.war

Workaround
Deployment fails if the class file depth (along with the file name) exceeds 255 characters. The suggested workaround:

  • Edit the server.xml file by hand
  • Create the directory to deploy to manually
  • Deploy the WAR file in the directory manually

4912181

On Linux, a null pointer exception is thrown when deploying an application using the wdeploy command-line utility. This happens at the end of the deploy, and only if it succeeds.

Workaround
The error seems to occur when wdeploy reads the stdout/stderr after execution of the reconfigure script following the deploy. The reconfigure should go through, but you should check to see if the server did indeed reconfigure by looking in the errors log for the reconfigure message. If the message is not there, then run the reconfigure script manually.

Web Container

The following table lists the known issues in the Web Container.

Table 17  Known Issues in the Web Container

Problem ID

Description

4903162

Issue on Windows related to the case of url-patterns.

Per the Servlet specification, url-pattern elements in web.xml are treated in a case sensitive manner. This may lead to unexpected behavior for Windows users (for example, if a client makes a request for index.HTML, expecting this to match index.html).

WebDAV

The following table lists the known issues in WebDAV.

Table 18  Known Issues in WebDAV

Problem ID

Description

4892017

Unable to rename or move a resource if the parent directory is locked exclusively.

This occurs when DAV clients send the incorrect If: header. For example, if you connect to the Web Server using Macromedia Dreamweaver or DAV Explorer, create a collection, and then lock the collection with depth infinity (which locks all of its resources as well), you will not be able to rename or move a resource. Adobe® GoLive® sends the correct If: header only if the lock’s owner href matches auth_user. In all other cases with GoLive, the wrong header will also be sent.

4902651

Lock Management screen in the Virtual Server Manager does not display the lock information properly for hard links.

Symbolic links (hard and soft) are not supported by the WebDAV implementation in Sun Java System Web Server.

How to Report Problems and Provide Feedback

If you have problems with Sun Java System Web Server 6.1 SP3, contact Sun customer support using one of the following mechanisms:

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

Sun Welcomes Your Comments

Sun is interested in improving its documentation and welcomes your comments and suggestions. Send your comments to Sun using the "Send comments" link at:  http://docs.sun.com/

Please include identifying information with your comments, such as the book’s part number and title.

Additional Sun Resources

Useful Sun ONE information can be found at the following locations:

Copyright © 2004 Sun Microsystems, Inc. All rights reserved. Sun Microsystems, Inc. has intellectual property rights relating to technology embodied in the product that is described in this document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S. patents listed at http://www.sun.com/patents and one or more additional patents or pending patent applications in the U.S. and in other countries. SUN PROPRIETARY/CONFIDENTIAL. U.S. Government Rights - Commercial software. Government users are subject to the Sun Microsystems, Inc. standard license agreement and applicable provisions of the FAR and its supplements. Use is subject to license terms. This distribution may include materials developed by third parties. Portions may be derived from Berkeley BSD systems, licensed from U. of CA. Sun, Sun Microsystems, the Sun logo, Java and Solaris are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. in the U.S. and other countries.

 

Copyright © 2004 Sun Microsystems, Inc. Tous droits réservés. Sun Microsystems, Inc. détient les droits de propriété intellectuels relatifs à la technologie incorporée dans le produit qui est décrit dans ce document. En particulier, et ce sans limitation, ces droits de propriété intellectuelle peuvent inclure un ou plusieurs des brevets américains listés à l'adresse http://www.sun.com/patents et et un ou des brevets des applications de brevet en attente aux Etats - Unis et dans les autres pays. Propriété de SUN/CONFIDENTIEL. L'utilisation est soumise aux termes du contrat de licence. Cette distribution peut comprendre des composants développés par des tierces parties. Des parties de ce produit pourront être dérivées des systèmes Berkeley BSD licenciés par l'Université de Californie. Sun, Sun Microsystems, le logo Sun, Java et Solaris sont des marques de fabrique ou des marques déposées de Sun Microsystems, Inc. aux Etats-Unis et dans d'autres pays. Toutes les marques SPARC sont utilisées sous licence et sont des marques de fabrique ou des marques déposées de SPARC International, Inc. aux Etats-Unis et dans d'autres pays.