Sun Java System Web Server 6.1 SP8 Release Notes


The following table lists the known issues in Installation.

Table 18 Known Issues in Installation

Problem ID 



JDK only upgrade results in disabling search. The user receives an exception, and the search page is not accessible from the GUI. 

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


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 not install the Web Server into a directory with spaces in the name.


On the Windows platform, the Sun Java System Web Server installer does not accept 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 field allows you to type up to 256 characters.


On the Solaris platform, Control-B does not work on screens that follow the Fully Qualified Domain Name screen in the installer, starting with the User and Group Name screen.

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


On the AIX platform, Control-C makes the terminal screen hang during installation. 

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


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: