Sun Java System Web Server 7.0 Update 3 Release Notes

Core

The following table lists the known issues in the core of Web Server.

Table 5 Known Issues in Core

Problem ID 

Description 

6296993 

When there is an error executing an obj.conf directive, the filename and line number where the offending directive was found are not logged.

6365160 

When server.xml schema validation fails due to a data type constraint violation, it displays an error message that does not describe the set of valid values for the element.

6378940 

All HTTP header parsing error are not logged with the client IP and a description of the error.

6470552 

set-variable SAF could not set predefined variable.

6486480 

service-nsfc-dump entry hit counts are 0 with <replacement>false</replacement>.

If <replacement>false</replacement> is specified in server.xml file, entry hit counts show as 0 in the service-nsfc-dump output. However, the cache hit counts are displayed correctly.

6489220 

Server treats non-interpolated strings that contain $$ character constants as interpolated.

When a parameter value contains a $$ escape, the server constructs a PblockModel for the parameter block. This is unnecessary because $$ is a constant.

6641109 

Webserver crashing configured with an NFS-mounted docroot directory

Web Server crashes if NFS file is removed or replaced, while using NFS and MediumFileSizeLimit >0. Therefore, you should not use MediumFileSizeLimit>0, if the document root is mounted over NFS.

Workaround

When Web Server documents are residing on an NFS mount, as in NFS client, set MediumFileSizeLimit to 0 in nsfc.conf.