Sun Java System Web Server 7.0 Release Notes

Core

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

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

6366843 

Limited capability for searching web applications, servlet , virtual server or nodes by names in core monitoring.

6368605 

Configuration error can cause child processes to be re-spawned in a loop.

If a configuration error is introduced after server startup, for example, obj.conf is deleted, and a child process is killed, the primordial process attempts to re-spawn that child process in an infinite loop.

6375367 

Improper error response to time-out following incomplete request.

If you telnet to Web Server, press Enter, and wait for the time-out, the following error response is returned:  

HTTP/1.1 400 Bad Request

Your browser sent a message this server could not understand.

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.

6479062 

Cannot dynamically reconfigure HTTP listener family. The Instance does not start on setting the protocol family to nca.

6485965 

If-modified-since processing is slow.

The server's handling of If-modified-since headers assumes that the header field value will typically match a previously sent Last-modified header field value. This is true of normal, real world clients. This is not true, however, of the SPECweb2005 driver.

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.

6489269 

'external' expression function with quoted path is not working.

6492407 

Front-end file accelerator cache.

Depending on ACLs and obj.conf configuration, a front end accelerator cache can service static file requests for URIs that were previously processed using NSAPI. The accelerator cache must work with the default configuration.

6496332 

File cache does not store small files on the heap and send large files with sendfilev.

With <sendfile>true</sendfile> in server.xml, the server should use sendfilev() only for files that does not fit in the heap. This enables the server to use writev() for small files and sendfilev() for large files.

6498452 

Server should not respond with '413 Entity Too Large'.

The server currently responds with a 413 Entity Too Large message when the request header is too big. 413 Entity Too Large message refers to the entity, not the header.

6498928 

Output directives are not invoked for 0-byte files.

Output directives are not invoked for 0-length responses unless protocol_start_response() is called. send-file does not call protocol_start_response() function. Output directives are not invoked when sending 0-byte files.

6501180 

Buffer-size 0 does not work.

If <buffer-size>0</buffer-size> is specified in server.xml, the server fails to correctly serve the files.

 

6502258 

Server crash with large output buffers.

If the output stream buffer size is bigger than the input buffer size, the server might attempt to buffer data at an invalid address. The default input buffer size is 8192 bytes.  

6504755 

Cannot disable access logging in default server instance.

The value of the <access-log> <enabled> element is ignored in the server.xml file.

6505390 

Accelerator cache does not handle ssl-unclean-shutdown properly.

The accelerator cache does not interact correctly with the AuthTrans fn="match-browser" browser="*MSIE*" ssl-unclean-shutdown="true" directive in the default configuration. When such a directive is present, the accelerator cache applies the "unclean shutdown" setting to every connection, regardless of the browser used.

6432375 

On HP-UX, SNMP fails for some oid values.

Workaround

Due to lack of the HP-UX API support and complexity, network in and out traffic statistics is not implemented. Use HP tools for monitoring the traffic statistics. 

6483212 

On HP-UX 11.11, Web Server fails to start when max heap size is 2048 MBytes or greater.

Workaround

  1. Ensure that patch PHKL_28428 or its updated version is present on the system. If it is not present, install the patch.

  2. Type the following commands before starting the Web Server:

    • For 1500 MBytes to 2400 MBytes of Java heap: Type the following command before starting the Web Server:

      chatr +q3p enable /opt/sun/webserver7/lib/webservd

    • For 2400 MBytes to 3.8 GBytes of Java heap: type the following command before starting the Web Server:

      chatr +q3p enable +q4p enable /opt/sun/webserver7/lib/webservd

  3. Start the server.

    /opt/sun/webserver7/lib is the default location of the webservd binary.