These release notes contain important information about the Sun JavaTM System Web Server 7.0 Update 1 (Web Server) release. These notes address new features and enhancements, installation notes, known problems, and other late-breaking issues. Read this document before you begin using Web Server Update 1.
These release notes contain the following sections:
Web Server 7.0 Update 1 is an update release to the major release of Web Server 7.0.
In addition to the features and enhancements in Web Server 7.0 listed later in these release notes, Web Server 7.0 Update 1 supports the Java Platform, Enterprise Edition (Java EE) 5.0 and Web 2.0 technologies. The details of these features and enhancements are described in the sections below.
Web Server includes a Java Platform, Enterprise Edition (Java EETM) 5 compliant implementation of the Java Servlet 2.5 and JavaServer PagesTM (JSPTM) 2.1 technology specifications. Web Server provides the flexibility and reliability needed to design and deploy web applications that comply with Java technology standards.
Java Servlet technology provides web developers with a simple, consistent mechanism for extending the functionality of a Web Server and for accessing existing business systems. JSP technology provides a simplified and a fast way to create dynamic web content. JSP technology enables rapid development of web-based applications that are server and platform-independent.
For information about these technologies, see http://java.sun.com/javaee/5/docs/tutorial/doc/.
The JavaServer Pages Standard Tag Library provides custom tags that encapsulate core functionality common to many web applications. JavaServer Pages Standard Tag Library has support for common, structural tasks such as iteration and conditionals. It provides tags for manipulating XML documents, internationalization tags, and SQL tags. It also provides a framework for integrating existing custom tags with JavaServer Pages Standard Tag Library tags.
Web Server supports JavaServer FacesTM technology. JavaServer Faces is a user interface framework for building web applications.
For information about these technologies, see: http://java.sun.com/j2ee/1.4/docs/tutorial/doc/index.html.
Web Server supports the 32–bit version of the Java Platform, Standard Edition (Java SETM) 5.0 and Java Platform, Standard Edition (Java SE) 6. For the 64-bit version of Web Server, the 64–bit version of Java Development Kit (JDKTM) software support is available. The 64–bit version of Web Server is currently supported only on the Solaris Operating System.
The following table lists the JDK versions supported on various platforms:
Table 1 Supported JDK Versions
Operating System |
Supported Java SE Version |
Whether Co-packaged With Web Server |
64–bit Support (Yes/No) |
---|---|---|---|
Solaris SPARC |
5.0_09 6 |
Yes No |
Yes |
Solaris x86/AMD,AMD64 |
5.0_09 6 |
Yes No |
Yes |
Linux |
5.0_09 6 |
Yes No |
No |
Windows |
5.0_09 6 |
Yes No |
No |
HP-UX |
5.0_03 |
Yes |
No |
At the time of installation, you must specify a valid path for the JDK. To use the JDK version that is not co-packaged with the product, download the software from the following location:
JDK version 1.6.0: http://java.sun.com/javase/downloads/index.jsp
JDK version 1.5.0_03: http://www.hp.com/products1/unix/java/java2/jdkjre5_0/index.html
Web Server includes new accelerator cache technology that speeds the delivery of small files. The accelerator cache is automatically enabled and requires no configuration. For more information, see the File Cache Information section of the Sun Java System Web Server 7.0 Update 1 Performance Tuning, Sizing, and Scaling Guide.
You can configure FastCGI using the Admin Console as well as the Command Line Interface (CLI). You can also configure the FastCGI with Web Server using the configuration files.
For more information about using the FastCGI in Web Server 7.0, see the Sun Java System Web Server 7.0 Update 1 Administrator’s Guide.
Web Server provides plug-ins to integrate with the NetBeansTM Integrated Development Environment (IDE) 5.0, 5.5, and 5.5.1 versions for deploying and debugging web applications. NetBeans is a complete development environment to create Java Platform Enterprise Edition (Java EE) based web applications with the standard components.
In addition to the deployment of web applications, the plug-in also provides support for the following activities:
Manage instances, such as start or stop server instances
Enable or disable applications
Create server wide resources, such as JDBC resources and JDBC connection pools
For information about NetBeans, see: http://www.netbeans.org/kb/index.html.
For more information about using NetBeans with Web Server, see: http://webserver.netbeans.org.
Web Server provides support for writing regular expressions within the obj.conf file through the Admin Console. However, writing regular expressions through the Admin Console is limited to the form of <If>..</If> conditions for URL redirects.
For more information on using the Admin Console for writing regular expressions, see the Sun Java System Web Server 7.0 Update 1 Administrator’s Guide.
Web Server provides support for configuring the URIs, URI prefixes, URI wildcard patterns properties through the Admin Console and the Admin CLI.
For more information on using the Admin Console for configuring URI pattern properties, see the Sun Java System Web Server 7.0 Update 1 Administrator’s Guide.
For more information on using the CLI commands for configuring URI pattern properties, see the Sun Java System Web Server 7.0 Update 1 CLI Reference Manual.
Web Server can be configured to run as a 64–bit application on the SolarisTM, SPARC® and AMD64 platforms.
Web Server provides comprehensive command-line interface support, consolidated configuration, enhanced security with elliptic curve cryptography support, and clustering support. It also comes with a robust built-in migration tool that helps migrate applications and configurations from Web Server 6.0 and Web Server 6.1 to Web Server 7.0.
Sun Java System Web Server includes the following new features:
Web Server management infrastructure is based on the modern distributed Java Management Extensions (JMXTM) technology. JMX technology provides tools for building distributed, web-based, modular and dynamic solutions for managing and monitoring devices, applications, and service-driven networks. JMX helps to manage and monitor instances, configurations, and web applications across clustered Web Server deployments.
The Administration Server is a specially configured Web Server instance on which the administration applications are deployed. An administration instance runs on each node in the server farm. Of these nodes, one node is configured to be the Administration Server and the rest are configured to be Administration Nodes.
The web-based Administration Server is redesigned to make common tasks easier to access and complex tasks easier to accomplish.
The Administration Server includes the following new features:
Web-based wizards for performing most common tasks
Comprehensive command-line interface (CLI) support for server configuration and server administration tasks
Centralized configuration store
Support for deploying Web Server configuration information on multiple machines. This feature extends to support Web Server in a server farms and clusters.
Built-in management and monitoring of server clusters
For more information on using the administration interface to perform administrative tasks, see the Sun Java System Web Server 7.0 Update 1 Administrator’s Guide.
The command-line interface enables you to easily configure and administer the server.
The administration CLI has the following key features:
Embedded Java Command Language (jacl) shell for scripting
Extensible CLI, which enables you to add more commands by using the third-party plug-ins
Support for local and remote administration, configuration, and management of one or more server instances
Automatically completes commands when you type one or more characters and then press a tab key
Easy-to-use CLI-based operational modes including single mode, shell mode, and file mode
For more information on the commands, see the Sun Java System Web Server 7.0 Update 1 CLI Reference Manual.
Web Server is integrated with Sun N1TM Service Provisioning Server 5.2. Sun N1 Service Provisioning System is an application provisioning tool that eliminates the need for custom scripts. With the integration of Web Server with Sun N1 Service Provisioning System, as an administrator, you do not need to write custom scripts for installing multiple Web Servers in a datacenter environment or in a server farm.
Configuration files in Web Server are rearranged and consolidated to simplify administration.
In the earlier versions of Web Server, the configuration files in userdb were shared by all instances, while the information contained in these files was often instance-specific. In Web Server 7.0, configuration files from the userdb directory are removed. Their functionality is incorporated into the server.xml file in the config directory. Configuration files from the alias and httpacl directories are moved into the config directory. These changes consolidate instance-specific configuration information within the instance-specific config directory.
For information about the configuration files, see the Sun Java System Web Server 7.0 Update 1 Administrator’s Configuration File Reference.
The Java Naming and Directory InterfaceTM (J.N.D.I.) API provides seamless connectivity to heterogeneous enterprise naming and directory services.
Web Server provides out-of-the-box, seamless Java DataBase Connectivity (JDBCTM), technology and supports a wide range of industry-standard and customized JDBC drivers.
Web Server supports JDBC connection pooling, that is, a group of reusable connections for a particular database. Because creating each new connection is time consuming, the server maintains a pool of available connections to increase performance. When an application requests a connection, it obtains a connection from the pool. When an application closes a connection, the connection is returned to the pool.
For information on creating JDBC connection pools, see the Sun Java System Web Server 7.0 Update 1 Administrator’s Guide.
Web Server includes Java Web Services Developer Pack (Java WSDP) 2.0 and XML technologies. Web services developed by using Java WSDP can be deployed on Web Server as a web application by using the wadm command.
Web Server 7.0 provides support for security features such as XML Encryption, XML Digital Signature, and support for message security provider.
For more information on Java WSDP 2.0, see the following resource:
http://java.sun.com/webservices/jwsdp/index.jsp
Java WSDP 2.0 samples are located at the following location. These samples can be deployed on Web Server 7.0.
http://java.sun.com/webservices/downloads/2.0_preview_webservicespack.html
Web Server supports cluster-based session replication and failover. Session replication and failover provides high availability to web applications by replicating HTTP sessions from one server instance to another in the same server cluster. Because each HTTP session has a backup copy on a remote instance, a server failure that renders one instance in the cluster unavailable does not disturb session continuity.
For more information on Light Weight Session Replication support, Sun Java System Web Server 7.0 Update 1 Administrator’s Guide.
Web Server 7.0 introduces enhanced support for regular expressions and conditional processing in the obj.conf configuration file.
Key enhancements include the following:
Support for regular expressions
A restart Server Application Function (SAF) for restarting requests with a new URI
Support for dynamic SAF parameters that include expressions, variables, regular expression back references
<If>, <ElseIf>, and <Else> tags for conditional processing
Support for complex conditions that use and, or, and notoperators
sed-request and sed-response filters for rewriting request and response bodies
You can use these new features to define flexible URL rewriting and redirection rules such as those possible with mod_rewrite from the Apache HTTP server. Unlike mod_rewrite, regular expressions and conditional processing in Web Server 7.0 can be used at any stage of request processing, even with third-party plug-ins.
For more information on regular expressions and URL rewrite functions, see the Sun Java System Web Server 7.0 Update 1 Administrator’s Configuration File Reference.
In addition to the monitoring facilities in earlier versions of Web Server, Web Server adds the following enhancements:
Monitors Servlets, JSPs, and JavaServer Pages Standard Tag Library container characteristics
Monitors process and virtual server statistics from within the Administration Server
Integrates with System Management Agent on the Solaris 10 platform. Integrates with the Java Enterprise System Monitoring Framework (Java ES Monitoring Framework) that makes Web Server monitoring information available within the Java ES Monitoring Framework.
Accesses monitoring data as Management Beans (MBeans) using the Java Monitoring and Management Console (jconsole) script, Java ES Monitoring Framework or any Java Management Extensions (JMX) compliant client applications.
For more information on Monitoring feature in Web Server, see the Sun Java System Web Server 7.0 Update 1 Administrator’s Guide.
Reverse Proxy is integrated with Web Server. Reverse Proxy can be executed as an internal module. In Web Server 6.1, the Reverse Proxy plug-in had to be downloaded separately and installed.
Web Server provides GUI and CLI support for configuring the reverse proxy.
For information about configuring reverse proxy, see the Sun Java System Web Server 7.0 Update 1 Administrator’s Guide.
Web Server supports a wide variety of technologies that allow data encryption and validation, request authentication, and server process protection. Key security feature enhancements include the following:
Solaris 10 platform cryptographic framework support. For example, libpkcs11.so including support for UltraSPARC® T1 processor hardware acceleration.
Denial of Service (DoS) attack protection enhancements
Cross-site scripting protection through the native sed(1) based input filtering
Web services security:
IETF XML Digital Signature
W3C XML Encryption
Integrated Platform for Privacy Preferences (P3P) support
Web-based Distributed Authoring and Versioning (WebDAV) access control support
The Lightweight Directory Access Protocol (LDAP) auth-db is enhanced to make search expressions and match attributes configurable
The LDAP auth-db supports Microsoft Active Directory interoperability
Support for migration of certificate from Tomcat or other Java keystore file based repositories
Support for dynamically applied Certificate Revocation Lists (CRLs)
Sun Java System Web Server has always supported RSA keys. In addition to the continued support for RSA keys, Web Server 7.0 introduces support for Elliptic Curve Cryptography (ECC).
ECC is the next generation of public-key cryptography for mobile or wireless environments. ECC is based on a set of algorithms for key generation, encryption, and decryption for performing asymmetric cryptography.
Important features of ECC are:
Compared to traditional cryptosystems like RSA, ECC offers equivalent security with smaller key sizes that enable faster computations, lower power consumption and memory, and bandwidth savings.
ECC operates on elliptic curves. You must pick a curve and a key length. Curves are standardized and given names by various organizations such as, NIST, ANSI, and SECG. Because these standards include the key length, you only have to pick one of the predefined curve names. Web Server 7.0 supports all the curves currently specified.
For more information on how to use ECC in Web Server, see the Sun Java System Web Server 7.0 Update 1 Administrator’s Guide.
Web Server 7.0 supports Sun Java Studio Enterprise 8.1. Sun Java Studio software is Sun's powerful, extensible IDE for Java technology developers. Sun Java Studio 8.1 is based on the NetBeans software, and integrated with the Sun Java platform.
The plug-in for the Web Server can be obtained in the following ways:
From the companion CD in the Sun Java System Web Server Media Kit
By using the companion AutoUpdate feature of Sun Java Studio
From the download center for Sun Java System Web Server
Sun Java Studio 8.1 plug-in for Web Server works only with a local web server. That is, the IDE and the web server must be installed on the same machine.
For information about using the web application features in Sun Java Studio 8.1, see the following tutorial:
http://developers.sun.com/prodtech/javatools/jsenterprise/learning/tutorials/index.jsp
For more information about Sun Java Studio 8, visit:
http://www.sun.com/software/sundev/jde/
Web Server is available in the following languages:
French
German
Spanish
Japanese
Simplified Chinese
Traditional Chinese
Korean
Web Server can be installed on the Solaris, Linux, HP-UX and Windows operating systems. The following table summarizes platform support. For more information about installation requirements, see Required Patches in these release notes.
Web Server runs as a 32-bit application on Windows, Linux, and HP-UX.
Intel Itanium Architecture is not supported.
Minimum required memory for installing Web Server on the specified platforms is applicable when you are installing Web Server as a stand-alone product. If you are installing Web Server as part of Java ES, the minimum required memory might vary. For exact memory requirements, see the Sun Java Enterprise System 5 Release Notes for UNIX.
Vendor |
Architecture |
Operating System |
Minimum Required Memory |
Minimum Recommended Disk Space |
---|---|---|---|---|
Sun |
UltraSPARC |
Solaris 8, 9, 10 |
256 MB |
550 MB |
Sun |
AMD/x86 |
Solaris 9, 10 (x86) Solaris 10 (AMD64) |
256 MB |
550 MB |
Microsoft |
AMD/x86 |
Windows 2000 Advanced Server, Service Pack 4 Windows XP Professional Edition, Windows 2003 Server, Enterprise Edition |
256 MB |
550 MB |
Red Hat |
AMD/x86 |
Red Hat Enterprise Linux AS 3.0 (Update 4 or later), 4.0 (or later updates) |
256 MB |
550 MB |
Novell |
AMD/x86 |
SUSE Linux Enterprise Server 9 (or later updates) |
256 MB |
550 MB |
Hewlett-Packard |
PA-RISC 2.0 |
HP-UX 11iv1 (B.11.11) |
256 MB |
550 MB |
System virtualization is a technology that enables multiple operating system (OS) instances to execute independently on shared hardware. Functionally, software deployed to an OS hosted in a virtualized environment is generally unaware that the underlying platform has been virtualized. Sun performs testing of its Sun Java System products on select system virtualization and OS combinations to help validate that the Sun Java System products continue to function on properly sized and configured virtualized environments as they do on non-virtualized systems. For information about Sun support for Sun Java System products in virtualized environments, see http://download.oracle.com/820–4651.
Update your operating system with the latest applicable patches. Required patches are listed in the following sections.
x86 or SPARC users of Solaris 8, 9, or 10 Operating System should have the latest patch cluster installed. This patch cluster is available under “Recommended and Security Patches” on the http://sunsolve.sun.com/pub-cgi/show.pl?target=patchpage web site.
On a 32–bit Solaris (SPARC) platform, install SUNWlibC and SUNWlibCx packages, in addition to the patches listed in the sections below.
Web Server 7.0 installer determines if the required patches are installed on your machine, without them the installation fails. The following patches are required for successful installation and functioning of Web Server 7.0 on a supported platform.
If the patches available at http://sunsolve.sun.com are obsolete, download the most recent version of these patches as they include the latest bug fixes and product enhancements.
To know the Solaris Operation System version installed on your machine, see the /etc/release file.
The /etc/release file contains Solaris Operation System version information in the following format:
Solaris 10 6/06 s10x_u2wos_08 X86 Copyright 2006 Sun Microsystems, Inc. All Rights Reserved. Use is subject to license terms. Assembled 02 May 2006 |
Solaris 8 2/02
108434-18 — Shared library patch for C++ (for 32–bit version of Web Server)
108435-18 — Shared library patch for C++ (for 64–bit version of Web Server )
Solaris 9 Platform (SPARC)
Solaris 9 9/05
111711-12 — Shared library patch for C++ (for the 32–bit version of Web Server)
111712-12 — Shared library patch for C++ (for the 64–bit version of Web Server)
Solaris 9 Platform (x86)
Solaris 9 9/05
117172-17 — Kernel patch
111713-09 — Shared library patch for C++
For the 64-bit version of Web Server, you must check if the SUNWlxml package is installed on the server by running the command # pkginfo SUNWlxml which produces the following output:
system SUNWlxml The XML library |
This package is always installed with Solaris 10 standard installation, even if you choose the lowest level of installation METACLUSTER=SUNWCmreq, NAME=Minimal Core System Support.
If you do not want this package, you can either, remove it by using the pkgrm command or use a jumpstart image which lacks this package.
SPARC
119963-03 — Shared library patch for C++
x86
119964-03 — Shared library patch for C++
Some incompatible patches can affect Web Server startup and cause the server not to respond to requests. The following table lists such patches. If you have an incompatible patch installed on your machine, upgrade the patch to a recommended compatible patch.
Table 3 List of Incompatible Patches
Operating System |
Incompatible Patch |
Recommended Compatible Patch |
---|---|---|
Solaris 8 SPARC |
109147-37 (linker patch) 109147-38 (linker patch) 109147-39 (linker patch) |
109147–40 (linker patch) |
Solaris 9 SPARC |
112963-22 (linker patch) 112963-23 (linker patch) 112963-24 (linker patch) |
112963-25 (linker patch) |
Solaris 9 x86 |
113986-18 (linker patch) 113986-19 (linker patch) 113986-20 (linker patch) |
113986-21 (linker patch) |
The requirements for installing Web Server on HP-UX platform are as follows:
HPUX11i-OE B.11.11.0312 (HP-UX 11i Operating Environment Component)
HPUXBase64 B.11.11 (HP-UX 64-bit Base OS)
HPUXBaseAux B.11.11.0312 (HP-UX Base OS Auxiliary)
FEATURE11-11 B.11.11.0209.5 (Feature Enablement Patches for HP-UX 11i, Sept 2002)
HWEnable11i B.11.11.0412.5 (Hardware Enablement Patches for HP-UX 11i v1)
BUNDLE B.11.11 (Patch Bundle)
BUNDLE11i B.11.11.0306.1 (Required Patch Bundle for HP-UX 11i, June 2003)
GOLDAPPS11i B.11.11.0506.4 (Applications Patches for HP-UX 11i v1, June 2005)
GOLDBASE11i B.11.11.0506.4 (Base Patches for HP-UX 11i v1, June 2005)
JAVAOOB 2.03.01 (Java2 Out-of-box for HP-UX )
PHCO_29109 1.0 (Pthread enhancement and fixes)
PHCO_30544 1.0 (Pthread.h fix and new enhancement)
PHCO_29495 1.0 (libc cumulative patch)
PHCO_31923 1.0 (libc cumulative header file patch)
PHKL_25842 Thread Abort (or its superseded patch)
PHCO_35743 s700_800 11.11 (libc cumulative patch)
Daylight Savings Time (DST) will start in U.S.A from the 2nd Sunday of March and end on the 1st Sunday of November. This will impact the date and time rules of the operating system and JDK/JRE.
To make sure that log files contain the correct time in US time zones, and that Administration Server and Java Web Applications are not impacted by this change, do the following:
Download and use the appropriate operating system patches. You can download the Solaris patches from http://sunsolve.sun.com/search/document.do?assetkey=1-26-102775-1. For other platforms, download similar DST compatible patches from operating system vendor's web site. |
Upgrade the JRE to make sure that Administration Server and Java Web Applications are not impacted by this change. Download and use the appropriate JRE that has the fix for DST changes. JRE versions for the supported platforms are as follows: |
Solaris: 1.5.0_09 or later
Linux: 1.5.0_09 or later
HP-UX: 1.5.0.03 or later
Windows: 1.5.0_09 or later
The following browsers are supported with Web Server Admin Console:
UNIX® and Windows platforms:
Mozilla 1.7
Firefox 1.0.4 or 1.5
Windows platform:
Microsoft Internet Explorer 7
This section includes notes about installing, migrating and upgrading your Sun Java System Web Server. For detailed information about these topics, review the information in the Sun Java System Web Server Installation and Migration Guide. For known issues in this release of Web Server, see Known Issues in these release notes.
You cannot install Web Server to a directory that contains an earlier version of Web Server. You can, however, migrate the existing installation after installing Web Server to a new directory.
Web Server 6.0 and 6.1 configurations can be migrated. Direct migration from a Web Server version lower than 6.0 is not supported. Earlier versions such as Web Server 4.0 or later must first be migrated to Web Server 6.1, then to Web Server 7.0. For information about migrating from Web Server 4.0 or later to Web Server 6.1, see the latest Sun Java System Web Server 6.1 Installation and Migration Guide and the Sun Java System Web Server 6.1 Release Notes.
For detailed information on migrating from Web Server 4.1 to Web Server 7.0, and from all versions of Web Server 6.0 to Web Server 7.0, see the Sun Java System Web Server 7.0 Update 2 Installation and Migration Guide.
When you install Sun Java System Web Server 7.0 Update 1 over an existing installation of Sun Java System Web Server 7.0, the installer automatically carries out the upgrade.
If you have Sun Java System Web Server 7.0 installed, point the Sun Java System Web Server 7.0 Update 1 installer to the location of the Web Server 7.0 installation and then upgrade.
If you have installed Sun Java System Web Server 7.0 as part of Java ES 5, you are encouraged to install the following patches from the http://sunsolve.sun.com/pub-cgi/show.pl?target=patchpage web site to upgrade to Web Server 7.0 Update 1:
125437 for Solaris SPARC/SPARCV9
125438 for Solaris x86/x64
125439 for Linux
125440 for HP-UX
125441 for Windows
If you are using a localized version of Web Server, install the following patches for successful upgrade from Web Server 7.0 to Web Server 7.0 Update 1:
126331 for Solaris SPARC (8/9/10) (Solaris SPARC Localization patch id)
126332 for Solaris x86 (8/9/10) (Solaris x86 Localization patch id)
126333 (Linux Localization patch id)
For detailed information about upgrading from Web Server 7.0 to Web Server 7.0 Update 1, see the Installation and Migration Guide.
Web Server 7.0 Update 1 supports JavaServerTM Faces 1.2 technology. Most JavaServer Faces 1.1 applications are expected to work with Web Server 7.0 Update 1 without any modifications. However, there are some compatibility issues that might be encountered when migrating applications to JavaServer Faces 1.2 applications and such applications require modifications. The changes are documented in the JavaServer Faces release notes at https://javaserverfaces.dev.java.net/rlnotes/1.2_04/issues.html.
Sun Java System Portal Server 7.1, provided with Java ES 5 is not compatible with Sun Java System Web Server 7.0 Update 1. If you have deployed Sun Java System Portal Server 7.1 along with Web Server 7.0, you need to upgrade both servers rather than only Sun Java System Web Server 7.0. The required Sun Java System Portal Server 7.1 upgrade is available with Java Enterprise System 5 Update 1 or with the following patches available on http://sunsolve.sun.com/pub-cgi/show.pl?target=patches/patch-access web site.
124301 (SPARC)
124302 (x86)
124303 (Linux)
If you are using a localized version of Web Server, install the following Portal Server localization patches:
125301 (Solaris SPARC, Solaris x86 localization)
125302 (Linux localization)
The complete Sun Java System Web Server 7.0 Update 1 documentation is available at http://docs.sun.com/coll/1653.1.
This section lists the issues resolved in Web Server 7.0 Update 1.
This section lists the important known issues and limitations at the time of Web Server 7.0 Update 1 release.
The following table lists the known issues in the administration of Web Server.
Table 4 Known Issues in Administration
Problem ID |
Description |
---|---|
6364924 |
A node can be registered to multiple administration servers which may cause a configuration conflict. It is possible to register a node to a second Administration Server without canceling the registration with the first Administration Server. However, this leads to the nodes becoming inaccessible to both the Administration Servers. Workaround: On each registration, restart the administration node. The administration node will be available to the most recent Administration Server it has registered to. |
6379125 |
wadm command allows connecting to a node, shows a certificate and then throws a 'HTTP 400 Error'. When an administration node receives a connection, the administration node does not check the connection is from the Administration Server before proceeding. It not only prints an inappropriate error message, but also prompts the user to enter the password. |
6387762 |
Cannot access shell/system variables from wadm. Workaround: wadm does not inherit the shell environment variables. However, to make the shell variables it available to wadm, use "java::call System getenv env_var_name For example: For accessing the shell environment variable MAIL from within wadm, type the following command at the wadm prompt: wadm> java::call System getenv "MAIL" /var/mail/abc |
4793938 |
User and password dialog presented instead of directory index. By default, Web Server 7.0 does not send a directory index unless the user has been authenticated. Attempting to access a directory prompts the user to enter a user name and password. This occurs because the default Access Control List (ACL) in Web Server 7.0 grants the list access right only to authenticated users. Workaround You can grant the list access right to unauthenticated users using the Admin Console or by editing the default.acl file. For more information on how to grant list access right, see Configuring Access Control in Sun Java System Web Server 7.0 Update 1 Administrator’s Guide. |
6327352 |
Session replication enabled instances does not come up normally, if other instances in the cluster are not started. |
6393534 |
After migrating the Java keystore keycerts using the migrate-jks-keycert command, trying to list the migrated jks keycerts using the list-certs command, displays the CN, org and other information instead of the certificate nickname. |
6407486 |
While setting the SSL property using the wadm set-ssl-prop command, the server-cert-nickname property accepts any certificate nickname, instead of accepting only the server certificate nickname. |
6443742 |
The set-session-replication-prop CLI command does not work if the 'node' option is provided with a qualified domain name. Workaround Use the output of the list-nodes command for the valid names of the nodes in the set-session-replication-prop command. |
6464953 |
Setting digestauthstate property through the set-authdb-prop CLI does not validate the value and allows to set junk value for this property. |
6468570 |
Specifying "yes" at the wadm prompt crashes the CLI. |
6469676 |
When you try to connect to the Administration Server after the administration certificates have expired, an incorrect error message is displayed. |
6480600 |
The register-node command gives an incorrect error message when the Administration server runs out of disk space. |
6495446 |
If no disk space is available on the device, wadm throws an incorrect error message "Unable to communicate with the administration server". |
6502800 |
Executing the migrate-server command with both "--all" and "--instance" options does not result in an error. A warning or an error message should be displayed indicating that the user is attempting the set mutually exclusive options. |
6416328 |
The Start Instances. button in the Admin Console is enabled for instance which is already running. The buttons should be enabled or disabled based on the status of the instance. |
6418312 |
wadm allows you to define duplicate user properties. Adding duplicate user properties does not show an error message; however, a new user property is not created. |
6421740 |
There is no provision to create new Access Control List (ACL) file using the Admin Console or the CLI. |
6423432 |
On Windows, using an existing configuration, repeating the process of adding and removing the registered nodes causes validation failure. |
6426116 |
Clicking on the Version button in the Admin Console result in “file not found” warning in Administration error logs. |
6430417 |
MIME Types allows MIME value with multibyte characters. |
6442081 |
Text in Access Control List page is not formatted. |
6442172 |
User can be switched between `available' and `selected' lists in ACE even though the user is deleted from the authentication database. |
6446162 |
No warning is issued before the deletion of key or the digestfile authentication database. |
6446206 |
When a single user in group is deleted, an incorrect message “Group Saved Successfully" is displayed. |
6448421 |
Administration Interface allows you to create a new user with multi-byte User ID in the keyfile authentication database. |
6455827 |
User and Group table in the Admin Console displays the entire result in a single page. |
6461101 |
Labeling of the Request Certificate and Install buttons in the Admin Console Create Self-Signed Certificate page needs to be revised. |
6462057 |
Add and Remove buttons are enabled in new ACE window even if no items are present in the `Available' list. |
6464891 |
Admin Console truncates the display of server logs at 50 lines or 2 pages. |
6465382 |
No validation exist to check the entry of wrong country code in the certificate request wizard. |
6465421 |
In the Admin Console, no text field description is provided for virtual-server, authdb, dav collection, and event fields . |
6466336 |
Admin Console shows wrong JDK version while creating a new configuration. The JDK version displayed in the Admin Console is 5.0 u6 instead of 5.0 u7. |
6471171 |
Style formatting is lost after restarting the Administration Server from Nodes -> Administration Server General tab. |
6471367 |
Attempting to access the Admin Console in another tab of the same browser does not work. |
6471792 |
View Log displays result in a single page. Although the search criteria selected for record size is 25 log entries, the log displays the results in one single page even if there are more than 50 log entries. |
6472932 |
Token mismatch error is displayed when you remove the token password and then reset it in the Common tasks -> Select configuration -> Edit configuration -> Certificates -> PKCS11 Tokens page. |
6486037 |
The Virtual Server Management->Content Handling->Document Directories->Add should have a browse option to choose the path of a additional document directory. |
6492906 |
Message displayed about WebDAV collection locks in the Admin Console is misleading. If you specify the time-out value for the WebDAV collection as infinite, the Common Tasks->Select Configuration ->Select Virtual Server->Edit Virtual Sever ->WebDAV->Select collection page displays the message DOES NOT EXPIRE. What it actually means is that the lock does not expire automatically after a specified time or the time-out is infinite. |
6498484 |
Incorrect error message is displayed on setting empty token password using the `Set passwords' button. |
6498554 |
Admin Console displayed incorrect failure messages on certificate creation and deletion. |
6500157 |
Instance fails to restart if you try to edit a token password and deploy a configuration on an instance which is already running. |
6502287 |
The Admin Console displays an exception when you delete a configuration and click on the Migrate button. |
6502374 |
The Admin Console Review screen in wizards should only show fields that have values. |
6502793 |
During migration, the log-dir path permission is not validated. |
6504050 |
The Results page in all Admin Console wizards should be aligned properly. |
6266358 |
Cannot log in through the Administration CLI if the administration password has extended ASCII characters. |
6361329 |
The error-response file name should be validated. |
6365379 |
Inconsistent behavior while starting an unregistered administration node. |
6367282 |
Administration server starts with expired certificate; wadm should warn about expired certificates. |
6367751 |
The create-instance command fails on remote node intermittently and logs HTTP 400 error. |
6375505 |
The unregister-node command should also clean up certificates on the administration node. |
6408169 |
WebDAV lock CLIs do not work in a cluster environment. |
6408186 |
Multiple installations of the administration nodes on the same node that is registered to the same administration server should be not be allowed. |
6416369 |
Accessing the administration node URL results in Page Not Found error. As the administration node does not have a GUI, accessing the administration node URL results in Page Not Found error. |
6416705 |
The default server.xml should not contain the <stack-size> element. |
6422936 |
No validation for class path prefix and suffix, and native library path in JVM Path Settings in Java. |
6423310 |
The server.xml elements should be grouped based on functionality. |
6426108 |
Exception in administration error logs on creating new configuration with instance. |
6431984 |
Web Server should store its pid file and UNIX domain sockets in /var/run instead of /tmp. |
6441773 |
On Windows. Administration server moves the Web application files physically before stopping the Web application. |
6451307 |
Executing the create-instance command immediately after starting a remote node fails on the remote node. |
6454559 |
View server logs page throws error if the access log format is not in Common Log Format (CLF). |
6462515 |
The Admin Console misleads user with "Instance modified" message when runtime files gets created in the config directory. |
6462579 |
Trust store does not deleted on uninstalling the administration node after unregistering it with the administration server. |
6468132 |
The list-cert command does not list the certificates if the certificate nickname contains a colon. |
6468330 |
Changes made to the JavaHome property does not get saved after restarting the instance. |
6473577 |
<pkcs11> element not removed from server.xml even when child elements are absent. |
6473589 |
<pkcs11/> added to server.xml when token pin is set. |
6475536 |
No obvious way to reset the administration server password. Workaround
|
6489727 |
[JESMF CONFORM] CP when stopping should call MfManagedElementServer_stop(). |
6491749 |
Need better validation in certain text fields to prevent obj.conf file corruption. Most of the functional validation of the data in a form is done in the back end. The GUI has only minimal checks such as empty fields, integer values, and ASCII values. Hence, the GUI stores the data in the obj.conf when parsed gets corrupted . |
6493971 |
Admin Server does not time-out if the server instance restart does not respond. On UNIX systems, the Administration Server waits until the server instance is restarted when the restart-instance command is executed. If the instance is not successfully restarted, the Administration Server does not respond to requests. |
6497213 |
Executing the restart-admin command followed by the stop-admin command throws exception in administration error logs. |
6515745 |
SNMP master agent process fails to start on Web Server Workaround: Changing the tcp_xmit_hiwat value to a higher value like 262144 , peer SNMP master agent functions properly. Type the following command to change the tcp_xmit_hiwat value. # ndd -set /dev/tcp tcp_xmit_hiwat 262144 |
6534202 |
Cannot edit WebDAV collection properties through the Admin Console When a configuration is deployed on multiple nodes, the lockdb path must be a shared location mounted on the same path on all the nodes. Additionally, to list or expire locks in the lockdb from the Admin Console, the same path must be writable from the Administration Server. |
6545779 |
On Windows, wdeploy command fails if older version of libnspr4.dll is found in the system32 directory. Workaround Before calling Java, edit the wdeploy.bat file that is available in install_dir/bin directory. Change the path of the Java directory to install_dir/lib directory. This modification makes Windows look for libnspr4.dll in the install_dir/lib directory before it looks in system32 directory. |
6554691 |
The add-webapp command when used with JSP pre-compilation option does not delete the previously precompiled JSP files. |
6556820 |
The Admin Console or the Admin CLI does not provide support to add CA certificates to the Administration Server. |
6587832 |
On Windows, the Admin Console intermittently fails to come up. Workaround
|
The following table lists the known issues in the core of Web Server.
Table 5 Known Issues in Core
The following table lists the known issues in Web Server 7.0 documentation and online help.
Table 6 Known Issues in Documentation and Online Help
Problem ID |
Description |
---|---|
6474011 |
The basic-search.html has unclear description. |
The following table lists the known issues in the FastCGI.
Table 7 Known Issues in FastCGI
Problem ID |
Description |
---|---|
6485248 |
The fastcgi stub does not properly close all the processes when reuse-connection is set to true. Configure Web Server 7.0 to work with PHP as a FastCGI plug-in and set reuse-connection=true. When you shutting down the server or reconfiguring the server, the fastcgi() process and its child processes are left behind and not killed properly. |
The following table lists the known issues in the installation of Web Server.
Table 8 Known Issues in Installation
Problem ID |
Description |
---|---|
4988156 |
Installing the stand-alone product over an existing Java ES installation and vice-versa is not supported. Installing Web Server 7.0 as a stand-alone product over an existing Java Enterprise System (Java ES) installation is not supported. Java ES users of the Web Server must use the Java ES installer to upgrade to the newer version of the Web Server. |
6414481 |
Web Server cannot be installed without installing compat-libstdc++. Workaround: On newer versions of Linux, for example, Red Hat Enterprise Linux 3, install compat-libstdc++ before installing Web Server 7.0. |
6414539 |
Uninstalling the administration node does not delete itself from the administration server node. After installing the administration node and registering it with the administration server in the Node tab, the administration node is listed in the Node tab. When the administration node is uninstalled, the administration node entry remains in the Node tab. |
6287206 |
Cannot install if the setup is started from a shared folder on the network. On the Windows platform, unable to install the product when the installer setup.exe is started from a shared network folder on another machine. |
6311607 |
On Windows, installer crashes in CLI mode, if the administration password is >= 8 characters. If the administration user password is greater than eight characters, then any invalid input to the administration port, web server port, or the administration user ID crashes the installer. Workaround: When installing Web Server 7.0 on the Windows platform using the command-line interface (CLI), the administration password must be set to less than (<) eight characters. |
6408072 |
On Windows, need icons for objects in Programs folder. The objects in the Sun Java System Web Server 7.0 folder on Windows are created with default Windows program icons and do not have specific icons that denote Sun programs. |
6492144 |
The CLI installer does not handle ctrl+c while entering the password. The installer does not accept ctrl+c and hence the terminal becomes unusable. |
The following table lists the known issues in the migration and upgrade areas of Web Server.
Table 9 Known Issues in Migration and Upgrade
Problem ID |
Description |
---|---|
6407877 |
Incorrect migration occurs while migrating from Web Server 6.0 to 7.0 if the installed.pkg file is not found. In Web Server 6.0 to 7.0 migration, if the installed.pkg file is missing, Web Server incorrectly migrates the NSServlet entries in the magnus.conf file. |
6490124 |
6.x -> 7.0: Migrated scheduled events still points to 6.x paths in the server.xml file.
|
6502529 |
6.1->7.0: Migration does not handle relative path set for search-collection-dir correctly. During instance migration, specifying a relative path for the target path into which the search collections should be copied, results in the search collection directory being created with respect to the config-store. When the instance is instantiated, the indexes are created without properly migrating the search collections. |
6502769 |
6.x->7.0: Migration ignores any "document-root" NameTrans specified in the obj.conf file. |
6498806 |
On Windows, Web Server Admin Console does not appropriately warn users during migration. Administration Server does not detect if the selected new configuration or the service name already exists on Windows and hence does not appropriately warn the users to select a different configuration name or suggest a different configuration name as default. |
6500509 |
Web Server 7.0 migration tool is unable to successfully migrate from Web Server 6.1 if it has Root Certs installed in it. |
6559918 |
Unclear error message if CLI and Administration Server versions are incompatible. While upgrading Web Server 7.0 installation to Web Server 7.0 Update 1 , make sure that the entire setup CLI, Administration Server and all the Administration Nodes are also upgraded to Web Server 7.0 Update 1. This is because, Web Server 7.0 administration interfaces will not work correctly with Web Server 7.0 Update 1 administration interfaces. |
The following table lists the known issues in Sample Applications of Web Server.
Table 10 Known Issues in Sample Applications
Problem ID |
Description |
---|---|
6472796 |
sendmail.jsp shows incorrect file to be edited to specify resource.host for javamail sample application. Workaround To set javamail.resource.host, edit the javamail.build.properties and not the build.xml as specified in install_dir/samples/java/webapps/javamail/src/docroot/sendmail.jsp. |
6559735 |
Sample applications documentation must mention adding jar file to the class path in the properties file. In the install-dir/samples/java/webapps/security/jdbcrealm/docs/index.html, under 'Compiling and Assembling the Application' section, there must be a mention of adding JDBC driver jar file to class path suffix in the jdbcrealm.build.properties file. |
The following table lists the known issues in the search functionality of Web Server 7.0.
Table 11 Known Issues in Search
Problem ID |
Description |
---|---|
6413058 |
server.xml does not store the full file pattern for converting and including search . The schema does not store the full file pattern allowed by both the Admin Console and the search administration tools in this version of the Web Server. It also has no way to represent the full file pattern that might sometimes need migration from the previous versions of the Web Server. |
The following table lists the known issues in the security area of Web Server.
Table 12 Known Issues in Security
Problem ID |
Description |
---|---|
6376901 |
Limitation supporting basic and digest-based ACLs for resources in the same directory. If the server uses digest and basic-based ACLs in different parts of their doc tree, attempting to use both simultaneously on different files or resources in the same directory is not possible. |
6431287 |
TLS_ECDH_RSA_* require the server cert signed with RSA keys. Cipher suites of the form TLS_ECDH_RSA_* requires server to have an ECC keypair with a cert signed using RSA keys. Note that this precludes using these cipher suites with self-signed certificates. This requirement is inherent to these cipher suites and is not a bug. The server should detect and warn about wrong configurations related to these cipher suites but currently it does not do so. |
6467621 |
Request to the server fails with using of "Sun Software PKCS#11 softtoken". Refer to the following documents for additional info on configuring the Web Server with Solaris 10 libpkcs11: http://www.sun.com/bigadmin/features/articles/web_server_t1.html |
The following table lists the known issues in the session replication functionality of Web Server 7.0.
Table 13 Known Issues in Session Replication
Problem ID |
Description |
---|---|
6324321 |
Descriptive error message is not displayed when an error occurs remotely. When an exception occurs remotely, error messages are logged in the error log of the remote instance. However, the local instance currently displays a generic remote exception which does not clearly indicate which error log that the user must view. |
6396820 |
Session replication does not failover correctly when cookies are disabled on the client. |
6406176 |
When enabled, session replication should be the default session manager. After enabling session replication by using the Admin Console or the CLI, or by editing the server.xml file, session replication is not really enabled. Instead, sun-web.xml needs to be manually edited. |
The following table lists the known issues in the web container of Web Server.
Table 14 Known Issues in Web Container
Problem ID |
Description |
---|---|
4858178 |
Web container writes to stderr. |
6349517 |
Incorrect web application session statistics for MaxProcs > 1 mode. Web Server runs in multi-process mode. The MaxProcs configuration variable in the magnus.conf is used to set the maximum number of processes. If the value for MaxProcs is set to greater than 1, the Web Server uses mmap-based session manager so that the session could be shared among different JVMs. While collecting statistics from multiple processes, web application MBeans provide session for individual MBeans. There is no way to find the true number of sessions by seeing individual MBean's web application session statistics.
|
6394715 |
Web container deletes the disabled web application MBeans object. When the web application is disabled by setting the <enabled> element to false in the server.xml file, the web container deletes the web application's MBeans and hence treats it as a closed or deleted web application. Since disabled objects are deleted, statistics are also lost. |
6419070 |
No information is logged in error logs at the finest log level on successful JNDI resource creation. |
6422200 |
com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse does 1 byte reads. When reading the server.xml file, the first line containing the XML version number and the encoding is read 1 byte at a time. |
6432870 |
Servlet container collects statistics when stats enabled element is set to false in the server.xml file. |
6440064 |
Servlet container creates a thread per virtual server. |
6472223 |
Values of 'mail-resource' sub elements are not getting set on mail session object. |
6487083 |
NSAPIRequest.setupRequestFields is slow. com.sun.webserver.connector.nsapi.NSAPIRequest.setupRequestFields is slow primarily because of excessive String-->byte and byte-->String conversion when parsing Cookie headers. |
6493271 |
Java garbage collector activity is higher in Web Server 7.0 when compared against Web Server 6.1. The servlet container in Web Server 7.0 creates many Java objects. |
6497803 |
If a servlet is mapped to req URI formed by partial req + welcome file, the behavior is wrong. If a web container receives a valid partial request, the web container must examine the welcome file list defined in the deployment descriptor. The welcome file list is an ordered list of partial URLs with no trailing or leading /. The Web Server must append each welcome file in the order specified in the deployment descriptor to the partial request and check whether a static resource or a servlet in the WAR file is mapped to that request URI. The web container must send the request to the first resource in the WAR that matches. |
6501184 |
REQ_EXIT causes javax.servlet.ServletException. |
6567124 |
JSF Web Applications running on Web Server 7.0 may break when running on Web Server 7.0 Update 1. Web Server 7.0 Update 1 ships with JavaServer Faces 1.2 technology. All JavaServer Faces web applications are expected to work with Web Server 7.0 Update 1 without any modifications. However, there are a few known compatibility issues with JavaServer Faces 1.2 and might require applications to be modified to address these incompatibilities. The incompatibilities are documented in the JavaServer Faces release notes at: https://javaserverfaces.dev.java.net/rlnotes/1.2_04/issues.html. Java ES 5 Portal Server users are suggested to delay upgrading to Web Server 7.0 Update 1 until Java ES 5 Update 1 is released. |
The following table lists the known issues in the localized version of Web Server.
Table 15 Known Issues in Localization
The following table lists the known issues in the Java Enterprise System (Java ES).
Table 16 Known Issues in Java ES
Problem ID |
Description |
---|---|
6484181 |
Portal Server configures JVM stack size to 128K (too low) for Web Server 7.0 64–bit to start. If Web Server 7.0 is already configured in 64–bit mode, and the Portal Server installation is started, Portal Server configuration does not set stack size to 128K. However, if both Portal Server and Web Server are already installed and configured in 32–bit mode, switching to 64–bit mode involve series of manual steps that are described in the Workaround section. Workaround If Portal Server part of Java ES 5 is deployed on top of the 32–bit version of Web Server 7.0, and if you would like to start the server in 64-bit mode, perform the following steps:
|
6487041 |
schemagen/xjc/wsgen/wsimport scripts not present in Java ES Web Server installation. schemagen/xjc/wsgen/wsimport scripts are present in different locations in Java ES installation and stand-alone installation of Web Server. Workaround The scripts are part of the Web Services components. In a stand-alone Web Server installation, these scripts and JAR files are located in install_dir/bin and install_dir/lib directories respectively. In Java ES installation, scripts and JAR files are installed as part of the shared component and they reside outside the Web Server installation root. The location of scripts and JAR files on different platforms are listed below: Solaris OS:
Linux and HP-UX:
Windows:
|
6432106 |
Sun Java System Portal Server search throws exception after Web Server upgrade. Portal Server search functionality throws exception when upgrading Web Server from Java ES 4 to Java ES 5. Workaround Note – Move the existing libdb-3.3.so and libdb_java-3.3.so library files to an appropriate location, somewhere outside the Web Server's private directories. Once the Portal Server libraries are in a suitable location, that path must be specified for the <libdb-3.3.so path>:<libdb_java-3.3.so path> in the following commands. On Solaris platform, perform the following steps:
|
6504178 |
Migration logs reports a bogus "root is not a valid user" message on Java ES 5. While migrating from Java ES 4 to Java ES 5 on UNIX platforms, the migration log file reports WARNING: "root is not a valid user". This is incorrect as the "root" user is valid on that host. |
6453037 |
A lot of warnings/info messages displayed at Web Server startup on the standard output instead of routing these messages to the log file. |
6549580 |
Web Server running on Windows contains no description for the service and the description is not updated after applying Java ES Update 1 patches. |
6550622 |
When upgrading Java ES 5 software to Java ES 5 Update 1, Portal Server samples fail with JSF exceptions if you have upgraded only Web Server but not the Portal Server. For more information, see Compatibility Issues. |
If you have problems with Sun Java System Web Server, contact Sun customer support using one of the following mechanisms:
Sun Software Support services online at:
The telephone dispatch number associated with your maintenance contract
So that we can best assist you in resolving problems, please have the following information available when you contact support:
Description of the problem, including the situation where the problem occurs and its impact on your operation
Machine type, operating system version, and product version, including any patches and other software that might be affecting the problem
Detailed steps on the methods you have used to reproduce the problem
Any error logs or core dumps
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 part number and the title of the book.
To provide feedback on Sun Java System Web Server product, send email to mailto:webserver@sun.com.
Useful Sun Java Systems information can be found at the following locations:
Documentation for Sun Java System Web Server
Sun Software Products and Service
Sun Developer Information
Sun Developer Support Services
Software Support Services
Sun Support and Training Services
Support: http://www.sun.com/support
Training: http://www.sun.com/training/
Sun Consulting and Professional Services
http://www.sun.com/service/sunjavasystem/sjsservicessuite.html
Besides searching Sun product documentation from the docs.sun.com web site, you can use a search engine of your choice by typing the following syntax in the search field:
<search-term> site:docs.sun.com
For example, to search for "Web Server", type the following:
Web Server site:docs.sun.com
To include other Sun web sites in your search (for example, java.sun.com, www.sun.com, developers.sun.com), use sun.com in place of docs.sun.comin the search field.