Sun Java System Web Server 6.1 2005Q4 SP5 Release Notes

Sun Java System Web Server Release Notes

Sun JavaTM System Web Server 6.1 2005Q4 SP5 (hereafter referred to as Sun Java System Web Server 6.1 SP5) 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 SP5, 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.

The complete Sun Java System Web Server 6.1 documentation is available at http://docs.sun.com/app/docs/prod/sjs.websrv61#hic.


Note –

The existing Sun Java System Web Server 6.1 2005Q1 SP4 documentation as published under the prior Sun Java Enterprise System 2005Q1 collection, is valid for Sun Java System Web Server 6.1 2005Q4 SP5 and for Sun Java Enterprise System 2005Q4. You can access these documents at http://docs.sun.com/app/docs/coll/WebServer_05q1.


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, see Sun Java System Web Server 6.1 SP4 Programmer’s Guide to Web Applications.

J2SE Platform 1.4 JDK/JRE Support

Sun Java System Web Server supports Java 2 Platform, Standard Edition (J2SETM) 1.4. J2SE software is bundled with the Web Server and installed during installation. You can also install your own JDK at a later time, following installation of the Web Server. Sun Java System Web Server 6.1 includes JDK 1.4.1 for HP-UX and JDK 1.4.2 for other platforms.

The 64-bit Solaris SPARC release of Sun Java System Web Server requires a 64-bit JDK. On all other platforms, a 32-bit JDK is required.

J2SE Platform 1.5 JDK/JRE Support

Sun Java System Web Server supports Java 2 Platform, Standard Edition (J2SE) 1.5 and has been tested and certified with 1.5.0_01 on Solaris, Linux and Windows platforms.

The 64-bit Solaris SPARC release of Sun Java System Web Server requires a 64-bit JDK, preferably JDK 1.5.0_06.

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 meta data, 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 plug-in could install an NSAPI filter to intercept an XML page generated by another plug-in'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 plug-in.

For more information, see Sun Java System Web Server 6.1 SP4 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 Sun Java System Web Server 6.1 SP4 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 Sun Java System Web Server 6.1 SP4 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 Sun Java System Web Server 6.1 SP4 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 SunTM 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 SP5. The plug-in for the Web Server can be obtained in the following ways:

Please note that the Sun ONE Studio 5 plug-in for Sun Java System Web Server 6.1 SP5 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 plug-in 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 at http://developers.sun.com/prodtech/javatools/jsenterprise/learning/tutorials/cdshop.pdf.

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

Also see the following NetBeans training documents at http://www.netbeans.org/kb/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. 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 SP5 supports the Active Server Pages 3.0 specification through Sun ONE Active Server Pages version 4.0.1 (formerly Sun Chili!Soft ASP) and 4.0.2. 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 SP5 provides support for Sun ONE Active Server Pages 4.0.1 and 4.0.2 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 http://www.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

PHP, the popular page scripting language available from the PHP group (http://www.php.net), can be used with the Sun Java System Web Server using one of three supported APIs: CGI, NSAPI, and FastCGI. The PHP group provides detailed instructions on its Web site for configuring the PHP software to use any of the three supported APIs.

The CGI API is the most stable interface that can be used but will suffer from performance limitations inherent in CGI.

NSAPI utilizes the Sun Java System Web Server's native API to run the PHP software within the Web Server's memory. This configuration will provide the best performance, but risks crashing the server if non thread safe PHP modules are used.

The FastCGI interface provides a compromise between performance and stability by allowing the PHP software to remain running after serving requests while continuing to run outside of the Web Server's memory. If an unstable PHP module is used it will not cause the Web Server to crash. For this reason Sun recommends use of the FastCGI interface with the PHP software.

The FastCGI interface is supported with the Web Server via the installation of the FastCGI Add-On available from http://www.sun.com/download/products.xml?id=3f567f91.


Note –

The PHP software makes use of two environment variables to control the life cycle of PHP processes when run as a FastCGI process. PHP_FCGI_CHILDREN determines the number of PHP processes that will be created to respond to requests. PHP_FCGI_MAX_REQUESTS determines the number of requests a PHP process can respond to before terminating itself and being replaced with a new PHP process. Sun recommends against the use of PHP_FCGI_CHILDREN and recommends instead the FastCGI Add-On configuration parameter min-procs to control the minimum number of PHP processes.


NSS and NSPR Support

The version of NSS included in Sun Java System Web Server 6.1 SP5 has been upgraded from 3.9.5 (in version 6.1 SP4) to 3.10.1.0 (32-bit) and 3.11 (64-bit). NSS is a set of libraries designed to support cross-platform development of security-enabled server applications. Sun Java System Web Server 6.1 SP5 also includes NSPR 4.5.2.

Enhanced Hardware Accelerator Encryption Support

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

64-bit Support on Solaris 10 (SPARC)

As of Sun Java System Web Server 6.1 SP5, a new 64-bit Solaris SPARC release is introduced to complement the existing 32-bit Solaris SPARC release. Sun encourages administrators to continue to deploy the 32-bit release of Sun Java System Web Server. The 64-bit release may be of use in certain memory-intensive deployments as it enables administrators to configure a larger file cache and Java heap than the 32-bit release. However, existing plug-ins are not compatible with the 64-bit release; these plug-ins will need to be recompiled for the 64-bit release by the plug-in vendor. Java web applications that use native, non-Java libraries will also need to be recompiled.

The 64-bit release is compatible with 64-bit Solaris kernels on UltraSPARC processors. The 64-bit release cannot be used on x86 processors or with 32-bit Solaris kernels. The 32-bit release continues to be compatible with both 32-bit and 64-bit Solaris kernels.

Note that the 64-bit and 32-bit releases of Sun Java System Web Server are packaged and distributed separately. It is not possible to upgrade an existing 32-bit Sun Java System Web Server installation to a 64-bit installation. It is possible to distinguish the 32-bit and 64-bit releases by the version string that is displayed in the installer, at server startup, and in the server errors log as follows:

Release 

Version String 

32–bit 

Sun ONE Web Server 6.1SP5 

64-bit 

Sun ONE Web Server 6.1SP5 (64-Bit) 

Solaris PKCS #11 Support

For Web Server's SSL subsystem (NSS) to use external PKCS#11 token(s), you need to configure NSS with the modutil command to make it aware of the token(s). The Solaris libpkcs11 softtoken is a PKCS#11 compliant token which can be used with NSS. As an additional benefit on UltraSPARC-T1, systems using Solaris 10's libpkcs11 will make use of the platform crypto acceleration support.

Before using the libpkcs11 provider, initialize its password with pktool:

% pktool setpin

Run the modutil command without any arguments for usage information. For example, to add the Solaris 10 libpkcs11 library as a PKCS11 token in NSS,

For further details on configuring NSS, see manpages and references:

Supported Platforms

Sun Java System Web Server 6.1 SP5 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 SP4 Installation and Migration Guide.


Note –

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


Table 1 Sun Java System Web Server 6.1 SP5 Supported Platforms

Vendor 

Architecture 

Operating System 

Minimum Required Memory 

Recommended Memory 

Recommended Disk Space 

IBM 

PowerPC 

AIX 5.1*, 5.2, 5.3 

64 MB 

192 MB 

256 MB 

Hewlett-Packard 

PA-RISC 2.0 

HP-UX 11i 

64 MB 

192 MB 

256 MB 

Microsoft 

x86 

Windows 2000 Server SP4 or higher 

Windows XP 

Windows Server 2003 Enterprise Edition 

64 MB 

192 MB 

256 MB 

Sun 

SPARC** 

Solaris 8, 9, 10 

64 MB 

192 MB 

256 MB 

Sun 

SPARC** (64-bit) 

Solaris 10 

64 MB 

192 MB 

256 MB 

Sun 

SPARC**, x86  

Trusted Solaris 8 (Professional Services Engagement)***  

64 MB 

192 MB 

256 MB 

Sun 

x86 

Solaris 9, 10 

64 MB 

192 MB 

256 MB 

Sun 

x86 

Sun Linux 5.0 (Deprecated)**** 

64 MB 

192 MB 

256 MB 

Red Hat 

x86 

Red Hat Linux Advanced Server 2.1 

  • Linux kernel 2.4.9-e.3smp

  • glibc-2.2.4-26

  • ncurses-4-5.0-5

Red Hat Enterprise Linux ES 3.0 

Red Hat Enterprise Linux ES 4.0 

64 MB 

192 MB 

256 MB 

* AIX 5.1 is deprecated.

** 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 Sun Partner Advantage professional services highly recommended.

**** Support for Sun Linux 5.0 is deprecated and will be removed in the next release of the Sun Java System Web Server.

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

Solaris users must have the Sun recommended patch cluster installed, available in the Recommended and Security Patches section at http://sunsolve.sun.com.

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 SP5.

HP-UX 11i

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 – 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 SP5.

AIX 5.1

AIX 5.2

If Java Web applications are deployed on the Web Server, then as 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.

AIX 5.3

Deprecated or Modified Public Interfaces in Sun Java System Web Server 6.1

The following public interfaces in Sun Java System Web Server 6.1 may be deprecated or modified in non-compatible ways in a future Web Server release. These interfaces will remain unchanged within the Web Server 6.1 product. Scripts that rely on these interfaces may require updating in order to function with future Web Server releases.

Table 2 Deprecated or Modified Public Interfaces

Configuration File or Utility 

Description 

magnus.conf

Modified. Some functionality may be moved to other files. 

server.xml

Modified. Schema and functionality may be modified. 

nsfc.conf

Deprecated. Functionality may be moved to other files. 

dbswitch.conf

Deprecated. This file may be eliminated; functionality may be moved to other files. 

password.conf

Deprecated. This file may be eliminated; functionality may be moved to other files. 

file layout 

Modified. The configuration file structure may be modified. 

start, stop, restart, and rotate scripts 

Modified. The names and/or locations of these utilities may change. 

wdeploy application 

Deprecated. This utility may be eliminated; functionality may be integrated with other management utilities. 

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 SP4 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 SP5. For known issues in this release of Sun Java System Web Server, see Known Issues in these release notes.

Installation

Upgrade

When you install Sun Java System Web Server 6.1 SP5 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 SP5 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 SP5, refer to the Sun Java Enterprise System 2004Q2 Installation Guide.

Migration

Direct migration from a version of iPlanetTM Web Server lower than 4.1 to Sun Java System Web Server 6.1 SP5 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 SP5.

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

Product Documentation

Sun Java System Web Server includes a complete set of product documentation, which can be found at http://docs.sun.com/app/docs/prod/websrv#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 SP5. The following table lists the tasks and concepts described in each manual.

Table 3 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 (J2EETM 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) plug-ins 

NSAPI Programmer’s Guide

Implementing servlets and JavaServer PagesTM (JSPTM) 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

Accessibility Features for People With Disabilities

To obtain accessibility features that have been released since the publishing of this media, consult Section 508 product assessments available from Sun upon request to determine which versions are best suited for deploying accessible solutions. Updated versions of applications can be found at: http://sun.com/software/javaenterprisesystem/get.html. For information on Sun's commitment to accessibility, see http://sun.com/access.

Resolved Issues

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

Issues Resolved in 6.1 SP5

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

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

Problem ID 

Description 

6322443 

NSFC buffer size should be configurable (64-Bit). 

Additional Information: Use the new BufferSize nsfc.conf directive to configure the size of the buffer used to transmit file contents on cache misses. The following directive can be added to nsfc.conf to increase the buffer size from its default of 8192 bytes to 16384 bytes: BufferSize=16384

Larger buffer sizes may result in improved throughput at the cost of increased latency and memory utilization. 

6234284 

JES3 Web Server installation fails and/or core dumps if the Admin password contain shell meta-characters such as ;, $, &, ^, *. (. ), |, <, >, ', `,”, and \, etc in Admin password. 

6232465 

Include -N linker option for HPUX Web Server builds. 

6171389 

Input filter is called only for the first HTTP request when using Keep-Alive. All subsequent requests of the TCP connection are not being processed by the filter. 

6195820 

Global resources are not available to load-on-startup servlets. 

5042600 

Unable to migrate 6.0 SP7 Web Server instance to 6.1 SP2. 

6244615 

Web Server migration should correctly update RootCerts. 

6219618 

JES Web Server 6.1 SP2 failed to index PDF version 1.5 (Acrobat 6.x) doc for Search Collection Creation. 

6239342 

Cross-site scripting vulnerability in a default error page. 

4879994 

SSL: Data larger than 8k is lot when the request triggers new SSL handshake. 

Additional Information: By default Web Server can upload file of size up to 1MB (when client cert authentication is optional). To upload file larger than 1MB, increase the SSLClientAuthDataLimit limit in the magnus.conf file. In case of simultaneous uploading of very large files Web Server will use large chunk of memory. To minimize memory utilization do any of the followings:

  • If authentication is not required, turn off the authentication.

  • If authentication is required, make it mandatory by setting require=1 in the obj.conf.


PathCheck fn="get-client-cert" dorequest="1" require="1"

6229472 

.htaccess Require directive broken. 

6170938 

acceptlanguage does not work for User Document Directories. 

6180991 

Internal-Daemon Log Rotation does not work for files greater than 2GB. 

6254121 

.htaccess silently fails to protect resources which do not have a corresponding file. 

6185904 

New NSS error codes are not being handled properly (unknown error – 8048). 

6262885 

Switching from HTTPS to HTTP causes generation of new session. 

Additional Information: Set the isSecure attribute of the session cookie for the Web application under cookie-properties to either true or false in the webapp's sun-web.xml. The default value is true. In the following example, isSecure is set to false for the web-app by setting the parameter value to false. The sun-web.xml will look like:


<session-config>
         <cookie-properties>
           <property name="isSecure" value="false"/>
         </cookie-properties>
      </session-config>

6222728 

SNMP services fail in Web Server 6.1 SP2/SP3 on Windows 2000 platform. 

6273472 

Web Server 6.1 SP4 uninstall script displays an error message – `No such file or directory'. 

6259257 

Some PDF files fail to be indexed by the search engine. 

6253489 

ClassCastException thrown when nested includes are present in JSPs. 

6285847 

Requests with double `Content-Length' header should get rejected (HRS vulnerability). 

Workaround: Add the StrictHttpHeaders directive in magnus.conf and set its value to on.

6275413 

Incorrectly configured home-page SAF crashes server. 

Issues Resolved in 6.1 SP4

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

Table 5 Issues Resolved in Sun Java System Web Server 6.1 SP4

Problem ID 

Description 

6021153 

Required patch id 112396-03 does not exist. 

The patch #112396-03 listed as `required' in earlier release notes was incorrect. There is only #112396-02 patch, which fixes the BugId #4498984 (*fgrep* fails with `wordlist too large' for some older version of OS patchadd command). 

The correct patch number is: 112396-02. 

Solaris users must have the Sun recommended patch cluster installed, available in the Recommended and Security Patches section at: http://sunsolve.sun.com

Solaris 8 (SPARC)

  • Solaris 8 Update 7

  • Sun recommended latest Security and Recommended patch cluster.

Solaris 9 (SPARC and x86)

  • Solaris 9 Update 4 or above.

  • Sun recommended latest Security and Recommended patch cluster.

6066252 

client certs with AKI extension causes SEC_ERROR_UNKNOWN_ISSUER error. 

6092498 

SJWS 6.1 fails to validate a client cert with LDAP if the cert contains Czech characters. 

6171311 

Frequent errors encountered when running Web Server with JDK 1.5. 

6171784 

Web Server performance issue with certain error logging configuration. 

4925875 

i18-ko: no asterix search result with Korean word. 

6171950 

Precompiled JSPs do not work as expected with reload-interval param in sun-web.xml. 

Workaround: Use the property `use-precompiled' (set to `true' under JSP-config in sun-web.xml) to specify that the JSPs are precompiled and should never need to be compiled at runtime.

Sample sun-web.xml 


<sun-web-app>
<session-config>
<session-manager/>
</session-config>
<jsp-config>
<property name="use-precompiled" value="true" />
</jsp-config>
</sun-web-app>

5048940 

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

6177544 

libpassthrough.so not present after RPM installation of plug-in. 

6176231 

Sun Java System Web Server 6.1 SP4 Admin delete certificate (bin/https/admin/security) core dumps with NSS 3.9.3 beta. 

6173365 

Multiple package installers for same build of Web Server of Solaris SPARC/x86. 

5039633 

Update NSS to 3.9 series. 

5063134 

Java ES symlink not used for J2SE location. 

6067407 

Problems using ACL_LDAPSessionFree(). 

6173293 

Web Server always sets content type to text/html when servlet filter is set. 

6176264 

Web Server 6.1 SP4 Solaris x86 unable to start the SSL instance through the Admin GUI. 

6180677 

Web Server SP4 for JES3 is unable to upgrade on top of Web Server SP2 for JES2. 

6066139 

JSTLTCK - 16 tests fail while running Web Server with JDK1.5_beta2 release. 

6088595 

Admin throws exception with JDK 1.5.0_beta2 while creating/editing classes. 

4904913 

I18N search: `?' wildcard search with Japanese causes wrong match. 

Issues Resolved in 6.1 SP3

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

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

Problem ID 

Description 

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 

GUI doesn't seem to permit manage users in keyfile database. 

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. 

5056989 

Enable prefixing of hostname in session ID. 

Note: you can enable prefixing hostname in session ID (as in 6.0SPx) for the web-app by setting the value of the property prefixSessionIDWithHostname under manager-properties to any of the values, yes, true, or on, in the web-app'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: plug-in defined in certmap.conf does not load. 

6041356 

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

6057426 

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

Note that the location of the loadbal.so plug-in is: <server_root>/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. 

4898077 

Inconsistent behavior between HttpServerAdmin and iWS console. 

5013100 

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

5046634 

2 byte character in http header and plug-in 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 web-app'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 7 Issues Resolved in Sun Java System Web Server 6.1 SP2

Problem ID 

Description 

4536102 

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

4536194 

CGI subsystem makes blocking calls from NSPR user threads. 

4536739 

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

4615933 

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

4629796 

ADM:i18n: French Thread pool name displaying garbage on JA-NT (Internet Explorer and Netscape). 

4651056 

Web Server returns 404 for files starting with `..'. 

4651206 

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

4651207 

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

4652009 

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

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 <sun-web-app> tag; do not embed them in any other tag. 

4664945 

Internal Error from URL forwarding form. 

4666409 

Clearing the ErrorResponse CGI files name. 

4676934 

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

4676946 

No validation of virtual server settings form. 

4676950 

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

4682434 

CGI script fails that grabs environment variables fails to execute. 

4682894 

Cluster management - Selection of source server deselects target servers. 

4684775 

Async DNS is disabled by default. 

4707989 

Web-app/JSP: load-on-startup not working on JSP files. 

4704385 

Cluster: Null message in modify cluster when `OK' is clicked soon after reset. 

4705181 

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

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 GUI Edit listen socket, server will not start. 

4727597 

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

4721021 

Unable to access absolute URI on SSL enabled server. 

4727444 

Access Log reports incorrect data. 

4732877 

Urlhosts field does not accept more that one hostname. 

4745314 

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

4749239 

ACLI: Incorrect processing of ACL. 

4753601 

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

4754934 

Vignette NSAPI plug-in on Web Server 6.0 not functioning correctly when using HTTP1.1. 

4761188 

LDAP: Improve LDAP dynamic group performance for ACL'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 membership 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 member of group `b'. 

If you want to support nested group in such case, don't define this new config for LDAP authentication service (you won't get performance gain consequently.) Sample config: directory: 

ldapregular ldap://localhost:389/o=TestCentral

ldapregular: dyngroups fast 

4763653 

Validation required for the form elements in document preferences page. 

4764307 

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

4765709 

Admin: Configure Directory Service not validating binddn/password. 

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. 

4800173 

Performance issue with large ACL file in conjunction with many virtual servers. 

4808402 

Native authenticator support. 

4814097 

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

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 accommodate the actual load. 

4849907 

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

4855807 

AIX: Web Server hangs after restarted by watchdog. 

4858152 

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

4869527 

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

4862498 

New directory Service Screen not connected to interface. 

4870613 

Back button not working for frames in Netscape 7. 

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: 

<LS remap="ls1" port="8080" security="disabled"...servername="https://www.sun.com"/>

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. 

4894033 

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

4896881 

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

4897074 

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

4899105 

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

4905175 

WebDAV ACL settings are inherited into new Virtual Servers. 

4909378 

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

4903449 

Performance affected with multi-process mode and one thread. 

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. 

4908631 

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

4907288 

Cluster Management file transfer not working on Windows. 

4909678 

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

4910266 

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

4904088 

Migration final page needs to HTML encode the `<' and `>' characters. 

4908986 

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

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. 

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. 

4913228 

Missing quote in oracle script for jdbcRealm sample application. 

4910869 

NSFC enhancement needed. 

Add the ReplaceFiles nsfc.conf directive.

When ReplaceFiles=true (default), the existing file cache behavior 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. 

4910272 

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

4912254 

Web Server installation failed due to `set -o noclobber' in .env. 

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. 

4911550 

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

4911633 

Change Password for the user is not working. 

4913566 

The URL Forwarding Editing Page is not consistent. 

4919473 

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

4913289 

Help on `Edit Virtual Class' doesn't give complete criteria for VS class deletion. 

4916331 

Keep-alive connections can hang under light load. 

4925475 

The server.xml createconsole attribute is ignored. 

4925938 

Getting Null Pointer exception if user mistakenly edits the VS Admin URL. 

4929848 

Performance: Web Server polls kstat once per second. 

4926414 

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

4935797 

certmap.conf file location mis-represented. 

4930327 

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

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. 

4930329 

Default values of maxpropdepth is poorly chosen. 

4932995 

The leading `/' is being removed when deleting Web application through Admin GUI. 

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 a new virtual server after migration causes $user: unable to find value. 

4941027 

Cross site scripting in Sun Web server Webadmin interface. 

4948397 

Web Server 6.1 SP1 SNMP is not working. 

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. 

4940040 

Administrator's Configuration File Reference defines nonexistent TYPE element. 

4942750 

Search example is incorrect. 

4943631 

Wrong documentation on Thread pool config file. 

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. 

4940418 

Third-party profiler support for bytecode instrumentation. 

4943329 

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

4947065 

The search web-app 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...). 

4954789 

Web Server deployment fails with ClassCastException. 

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. 

4951860 

httpagt depends on NETSITE_ROOT variable. 

4957158 

fc_open fails when running specweb99 on x86 build. 

4952492 

MOVE method should `rename' files when possible. 

4958571 

PR_NetAddrToString performance is less than expected. 

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. 

4950653 

`Null' is displayed for QoS vsclass values. 

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.

4961864 

Web Server hangs when using rotate-callback. 

4962059 

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

4969637 

Minor coding error in send-error SAF. 

4961999 

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

4962624 

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

4963483 

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

4968422 

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

4966497 

Perf Dump data for Average Queueing Delay is not correct. 

4970955 

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

4972573 

Incorrect behavior in web-apps-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. 

4970273 

FastCGI beta libraries are in RTM Web Server packages. 

4976953 

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

4976490 

Log messages truncated. 

4975675 

Dynamic reconfiguration fails when server is under load. 

4976910 

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

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. 

4975782 

Can't delete external JNDI reference. 

4970188 

RPM can't locate system umask. 

4971298 

pkgchk -n fails for Web Server package in JES. 

4986761 

Web Server 6.0 migration fails. 

4989231 

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

4988104 

Edit virtual servers page should update the connections value correctly. 

4986700 

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

4991888 

Storing the wrong file name for key file configuration. 

4992739 

Cannot start Web Server instance, after modifying its classpath suffix. 

4995447 

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

4995489 

Solaris x86: distributed Admin cannot be enabled. 

4991775 

Validation of cookie name in cookie example servlet. 

5002905 

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

5012107 

POST request body consumed twice when using bad plug-in. 

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. 

4844616 

dbswitch misconfiguration causes crash. 

4854698 

Plug-in 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. 

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, for example web.xml. 

4939370 

Web container thread names are not unique. 

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. 

4932547 

Tomcat AuthenticatorBase returning 500 instead of 403. 

4946762 

Out of box default realm should be native. 

4948123 

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

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. 

4968882 

htconvert does not work on 6.1 style server.xml. 

4960873 

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

4973927 

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

4976277 

Using JDK 1.4.1 provided JNDI connection pool for LDAP pooling. 

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 `//'. 

4996219 

Webservd leaks memory on RedHat Linux Advance Server 3.0. 

4997593 

Poor integration between NSAPI srvhdrs and HttpServletResponse headers. 

4997756 

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

4997838 

Web Server 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. 

Issues Resolved in 6.1 SP1

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

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

Problem ID 

Description 

5060906 

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

Additional information: As for 6.1 SP1, if a directory does not have an index file such as index.html, index.jsp, home.html, etc, then while turning on ACL authentication anyone with read and write permission are denied the list access even though this directory is unprotected.

Workaround: To revert back to the previous behavior of 6.1, change the default ACL so that anonymous users are allowed list privileges. Make the changes as follows:

allow (read, execute, info, list) user = "anyone"

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 GUI 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 meta tags are always indexed. Functionality has been added that now allows arbitrary meta tags 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 meta tag names (note that the Author , Subject, and Keywords meta tags are always indexed, regardless of this setting).

  • To index the meta tags resulting from the conversion of PDFs and other types of documents, this configuration must use the name of the meta tag, 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 meta tag 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 9 Issues Resolved in Sun Java System Web Server 6.1

Problem ID 

Description 

4869693 

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

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 plug-in.

4820513 

digestauth plug-in 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 plug-in crashes for a particular type of request.

4849914 

Memory leak in digestauth plug-in for a particular type of request.

4855546 

Log analyser vulnerability. 

4858026 

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

4867887 

Basic authentication fails for users with user IDs 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 SP5 release. The issues are listed by category:

General

The following table lists General known issues.

Table 10 General Known Issues

Problem ID 

Description 

6198559 

JES3: Patch Upgrade of Web Server on Linux throws false `Uninstall' notification. 

Administration

The following table lists the known issues in Administration.

Table 11 Known Issues in Administration

Problem ID 

Description 

6301761 

ACL applet may fail to load with Mozilla 1.4 and Firefox 1.0.6. 

6197731 

Internal Error on accessing Admin Server. 

Workaround: If Web Server 6.1 SP4 is installed on a Windows machine which has Directory Server (versions 5.2 patch 3 or lower) installed, you may run into problems with the Web Server Admin Server. It is advisable to install the Web Server and Directory Server on separate machines to avoid issues. This issue is applicable only on Windows platforms.

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. 

Workaround: Comment out 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 multi-byte 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 date stamp in the log filename is not consistent with the date stamp in the log file entries. 

Workaround: If the date in the log 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.0 SP4, 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 Admin GUI. 

4888696 

The Add Server page in the Admin GUI 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 GUI, 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 

Super users 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 `Yes', with a 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.

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

6284698 

Web Server not operational when installed as non root user. 

Workaround: Start the Web Server instance from the command line instead of using the Web Admin console.

6078104 

JSP applications are not accessible from WS6.1 when passthrough plug-in is configured. 

Workaround: Change the line from the service directive of passthrough:

From: 

Service type="magnus-internal/passthrough" fn="service-passthrough"servers="http://server:port"

To: 

Service fn="service-passthrough" servers="http://server:port"

4841310 

Cannot 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.

4991278 

No Admin GUI feature available to delete JSP ClassCache files. 

6316262 

Admin GUI does not reflect changes made to the accesslog path. 

6316265 

Admin GUI says `Click Apply' for the changes to take affect but there is no `Apply' button for Admin Server. 

Core

The following table lists the known issue in Core.

Table 12 Known Issues in Core

Problem ID 

Description 

6363944 

webservd child process orphaned when Solaris crypto softtoken (libpkcs11.so) is used in S1WS6.1SP5 64-bit. 

Workaround: This problem occurs only when the server is explicitly configured to use the Solaris softtoken. If you have to use fork(), Runtime.exec(), or <!--#exec cmd="..."-->, do not configure the server to use the Solaris softtoken.

6313832 

Existing 32-bit plug-ins cannot be used with the 64-bit release. Attempting to load a 32-bit plug-in using the 64-bit Sun Java System Web Server release will result in an error message such as the following: 

Sun ONE Web Server 6.1SP5 (64-Bit) B10/28/2005 09:00

failure: CORE3170: Configuration initialization failed: Error running init function load-modules: dlopen of plugin.so failed (ld.so.1: webservd: fatal: plugin.so: wrong ELF class: ELFCLASS32)

Workaround: Use the 32-bit release of Sun Java System Web Server or contact the plug-in vendor to obtain a 64-bit release of the affected plug-in.

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 13 Known Issues in Documentation

Problem ID 

Description 

6359385 

Administrator's Configuration File Reference should document the magnus.conf variable MaxKeepAliveConnections value range for 64–bit server.

Additional Information: magnus.conf MaxKeepAliveConnections directive values range from 0 - 1048576 for the 64-bit server.

6358849 

Administrator's Configuration File Reference should document the MaxOpenFiles attribute in the nsfc.conf configuration file.

Additional Information: Details of the MaxOpenFiles attribute are as follows:

  • Attribute: MaxOpenFiles

  • Default Value: 1024

  • Description: Limit on the number of cached open file descriptors.

4964908 

No documentation available regarding feature upgrades.  

5065188 

6173274 

Administrator's Guide incorrectly describes a Find menu Passage Search option in the Advanced Search section. This menu option is not available.

6155266 

Administrator's Guide incorrectly describes the config log level.

Correction: The Web Server config level should be defined as follows:

Message indicate a misconfiguration.

6206074 

Administrator's Configuration File Reference describes an incorrect default value for the ChildRestartCallback directive.

Correction: The default value is no directive.

6170766 

Installation and Migration Guide describes an incorrect method of upgrading a newer version of Web Server in the Before You Install Sun One Web Server section.

Correction: To upgrade Sun One Web Server 6.1, which is a part of the Sun Java Enterprise System 1, users must use patchadd.

6170769 

Administrator's Configuration File Reference has incorrect information about the AdminLanguage directive.

Correction: The AdminLanguage directive is only applicable to the language displayed in the log messages and not the GUI.

6173273 

Administrator's Guide has a typo error under section Choosing MIME Types.

Correction: The sentence should be read as follows: For more information, see the MIME Types page in the online help and Using Virtual Servers.

6173133 

NSAPI Programmer's Guide describes an incorrect example of a NSAPI Function Reference.

Correction: The example should be read as follows:

FilterMethods methods = FILTER_METHOD_INITIALIZED;

6173272 

Administrator's Guide incorrectly documents the supported version of Java as `1.4.1_03'.

Correction: 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.  

5016571 

Online Help page under Generic Thread Pools gives invalid information.

5029460 

Administrator's Guide documents an incorrect certmap.conf configuration.

The description of certmap.conf in the 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=UScertmap sun2 ou=Sun Certificate Authority,o=Sun, c=US

Correction: The two lines should be read as follows:

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

5031366 

Invalid links in the online version of Administrator's Guide

4968568 

Administrator's Configuration File Reference guide's description on the ConnQueueSize directive is not clear.

4975161 

Administrator's Configuration File Reference does not document the optional parameter `block-size' for pool-init.

5002190 

Administrator's Guide doesn't contain information about the htpasswd command utility.

Additional Information: The htpasswd command is used to generate or modify a password file suitable for use with the htaccess access control mechanism.

htpasswd Usage:

htpasswd [-c] passwordfile username [password]

-c creates a new password file.  

As noted, -c creates a new password file by overwriting an old one if it already exists. Without -c, the command will modify the existing file by either updating the user's password (if user already exists) or adding a new user with the given name.

If the optional password argument is not given, it will prompt interactively for the password to assign.  

Note that htaccess is not the preferred access control mechanism in Web Server. Wherever possible, use ACLs instead. 

5002192 

Administrator's Configuration File Reference has incorrect information about the loglevel attribute.

Correction: The loglevel description should be read as follows:

Controls the default type of messages logged by other elements to the error log. Allowed values are as follows, from highest to lowest: finest, finer, fine, info, warning, failure, config, security, and catastrophe. 

5020640 

NSAPI Programmer's Guide does not document the %duration% flex-log format variable.

5029321 

Administrator's Configuration File Reference documents the <Client uri="*foo*" uri="*~bar*"> directive incorrectly.

Correction: In some cases the evaluation can be rewritten to occupy a single evaluation statement:

<Client uri="*foo*~*bar*">.

It is functionally the same as  

<Client uri="*foo*" uri="~*bar*">.

5038534 

Administrator's Configuration File Reference has incorrect default value for the LogFlushInterval directive.

Correction: The correct default value for the LogFlushInterval directive is 2 seconds.

5043491 

Incorrect online help content. 

4781137 

Administrator's Guide has the following incorrect information:

  • The path where libdigest-plugin.ldif exist is not defined in the guide.

    Additional Information:libdigest-plugin.ldif is available at <server-root>/plugins/digest/libdigest-plugin.ldif.

  • Information to configure the Web Server to process digest authentication (set the digestauth property of the database definition in dbswitch.conf) is given without describing the procedure to do it.

  • libdigest-plugin.so is incorrectly mentioned as libdigest-plugin.lib.

  • Description of iplanetReversiblePassword is missing.

4823362 

Administrator's Guide needs to be updated with additional information regarding ACL.

Additional Information: If there are more than one ACLs that match, the server uses the last statement that matches. The default ACL is bypassed as the uri ACL is the last statement that matches.

4862795 

Administrator's Guide's description on the Archive Log File page is not clear.

Correction: The following note to be added to the document to make the description more clear: The user can archive or delete the old log files (this activity is not done by the Web Server).

5046588 

Installation and Migration Guide incorrectly documents the supported version of Sun accelerator hardware.

Correction: The supported version of Sun accelerator hardware is 500 and 1000.

5052605 

The NSAPI Programmer's Guide does not clearly specify that content-type needs to be in lower case.

5053339 

Online Help — Directory Indexing information is missing in Administrator's Guide and online help.

5062560 

Installation and Migration Guide does not document the method of disabling the start-on-boot option.

Additional Information: Users can disable the start-on-boot option as follows:

On Solaris and HPUX — Turn off by editing the S1WS_START_ONBOOT variable in the webserver01 script.

[Solaris] 

/etc/init.d/webserver01

[HPUX] 

/sbin/init.d/webserver01

On Linux — Delete the following links to disable it: 

/etc/rc.d/rc3.d/S75webserver01

/etc/rc.d/rc5.d/S75webserver01

6067059 

In Administrator's Guide any tags without content body should have `/' before the end `>' tag.

4928287 

All documents do not inform user the nonexistence of <instance>/lib directory.

Additional Information:This directory is not created by the installer. Users have to create the directory if it does not exist.

4970961 

Administrator's Configuration File Reference doesn't explain ChunkedRequestTimeout in detail.

6308091 

Administrator's Configuration File Reference — Wildcard pattern with tilde in ppath doesn't work as documented.

Correction: Users have to configure either of the followings:

Config 1

<Object ppath="*~*.gif*">AddLog fn=flex-log name="access"</Object>

Config 2

<Object ppath="*~*(.gif|.gif/)">AddLog fn=flex-log name="access" </Object>

6285234 

Administrator's Configuration File Reference incorrectly describes the default value of the StrictHttpHeaders directive as on.

Correction: The default value of the StrictHttpHeaders directive is off.

6067318 

Administrator's Configuration File Reference has insufficient information about the set-variable error parameter.

Correction: The description of the set-variable error parameter should be read as follows:

Sets the HTTP status code and aborts the request by returning REQ_ABORTED. To set the HTTP status code without aborting the request, use the set-variable error parameter along with the noaction parameter.

To rewrite an HTTP status code, use a <Client> tag to match the original status code and an Output directive to set the new status code. For example, the following would rewrite all 302 Moved Temporarily responses to 301 Moved Permanently responses: 

<Client code="302">Output fn="set-variable" error="301 Moved Permanently" noaction="true"</Client>

6281323 

Release Notes for Sun Java System Web Server 6.1 2005Q1 SP4 documents the incorrect version of Windows 2003 operating system.

Correction: The supported version of Windows 2003 for Web Server 6.1 SP4 is

Windows Server 2003, SP1 Enterprise Edition

6237209 

Release Notes for Sun Java System Web Server 6.1 2004Q3 SP3 doesn't include complete information regarding various RedHat Linux kernels.

6237303 

Release Notes for SUN ONE Web Server 6.1 does not list all patches that are required for Solaris SPARC.

Additional Information: 109326-09 is a required patch for Web Server 6.1 on Solaris 8.

6230379 

Administrator's Configuration File Reference incorrectly describes a remove-file() SAF.

Correction: The remove-file() is renamed to delete-file().

6208955 

NSAPI Programmer's Guide incorrectly documents the description of SERVER_SOFTWARE as MAGNUS_VERSION_STRING.

Correction: The NSAPI variable for SERVER_SOFTWARE is system_version().

4673436 

To have iWS recognize remote shares within Domain Controller environment. 

4841310 

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

5059527 

Web Server configuration files and scripts are writable by webservd. 

6320016 

Administrator's Configuration File Reference doesn't clearly define the default value of listenQ on Windows.

Correction: The default value of listenQ on Windows is 200.

Installation

The following table lists the known issues in Installation.

Table 14 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, ctrl+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 15 Known Issues in Migration

Problem ID 

Description 

4790457 

Can't change the document root of migrated server from 4.1. 

Workaround: Edit the migrated instance's obj.conf and server.xml manually. These files are located under <code><SERVER_ROOT>/<HTTPS-INSTANCE>/config directory.

In obj.conf change the line:


NameTrans fn=document-root root="<existing_doc_root>"

to 


NameTrans fn=document-root root="$docroot"

In server.xml under the relevant VSCLASS change the line:


<PROPERTY name="docroot" value="<existing_doc_root>"/>

to 


<PROPERTY name="docroot" value="<new_doc_root>"/>

6213097 

ktsearch.jar is not getting migrated correctly on Sun Java Enterprise System 3 (JES3). 

Workaround: Manually edit the server.xml file of the migrated instance to point to the correct path.

For Linux: /opt/sun/private/share/lib/ktsearch.jar

For Solaris Sparc: /usr/share/lib/ktsearch.jar

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 suppress them, upon migration these web-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 wish to upgrade the Sun Java System Web Server 6.1 that is installed as a part of Sun Java Enterprise System (JES), to the latest Service Pack, you will have to download and apply the relevant patches, for more details please refer to the JES 3 Migration and Upgrade guide.

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 16 Known Issues in Samples

Problem ID 

Description 

5014039 

Simple JSPs throw exception due to <distributable> tag in web.xml 

Workaround: Remove the tag <distributable></distributable> from the web.xml under the simple/src directory. Redeploy the web-app.

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 17 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.

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). 

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 

Security

The following table lists the known issues in Security.

Table 18 Known Issues in Security

Problem ID 

Description 

4898077 

Enable SSL, inconsistent behavior between HttpServerAdmin and iWS console. 

Workaround: Use the following 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 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 Chapter 16 of the Sun Java System Web Server 6.1 Administrator’s Guide, instead of (or in addition to) denying the list right.

6310956 

6298215 

When LDAP drops the connection because of inactivity (for example, timeout set on the LDAP), Web Server is unable to re-initialize the connection to LDAP. This only occurs when Web Server is installed as part of the JES3/JES4 install, the problem is not present with standalone (file-based) installation.  

Workaround:

  1. Copy the library libldap50.so from the file-based install of Web Server and paste it to the following location in your current setup: /opt/SUNWwbsvr/bin/https/lib

  2. Restart the Web Server.

Tools

The following table lists the known issues in Tools.

Table 19 Known Issues in Tools

Problem ID 

Description 

4905696 

On Windows, deployment fails if the class file depth (along with the file name) exceeds 255 characters. 

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 20 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 21 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 SP5, 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 Java Systems information can be found at the following locations: