Sun Java System Web Proxy Server 4.0.6 Release Notes

Known Issues

This section lists the more important known issues and limitations at the time of the Sun Java System Web Proxy Server 4.0.6 release. The issues are listed by category:

Administration

The following table lists the known issues related to the administration user interface.

Table 9 Known Issues in Administration

ID  

Summary 

6212701 

Conflicting error message is displayed when server instance fails to start. 

The chances of occurrence of this conflicting error message is minimal as the chances of the administration interface writing wrong information in the configuration file is minimal. It can only occur if the user manually writes wrong information into the configuration file.  

6231297 

The Restart Required link disappears if changes are made to the SOCKS configuration and the Proxy Server is restarted instead of the SOCKS Server. 

6484502 

Proxy Server administration interface is not localized. 

6509535 

Daylight Savings Time (DST) will start in USA 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 JRE.  

 

In the standalone version of proxy server, JRE version compatible with 2007 DST changes is bundled with the installer. However, you need to address the impact on the date and time rules of the operating system by installing the appropriate Operating System patches as explained in step 1 of the Workaround. 

 

For the JavaES 5 installation of proxy server, you need to install the Operating System patches and also the compatible version of JRE . Follow steps 1 and 2 of the Workaround. 

Workaround

  1. 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 the Operating System vendor's web site.

  2. For Solaris, Windows, and Linux, run proxy server with JRE 1.4.2_13. For HP-UX, run proxy server with JRE 1.4.2.12.

6558027 

On Windows, server identifier with multibyte characters causes server-side createInstance.exe error.

Caching

The following table lists the known issues related to caching.

Table 10 Known Issues in Caching

ID  

Summary  

6229823 

When a new partition is added a default section s0.0 is also created irrespective of the partition size. Warning messages are logged in the errors file. 

Workaround

Use the cbuild utility to add the new partition or delete the s0.0 folder under the new cache partition, and restart the proxy server.

The error messages can be ignored. 

Installation

The following table lists the known issues related to installation.

Table 11 Known Issues in Installation

ID  

Summary  

6205683 

Windows console installation fails. 

6255325 

The installer throws an exception and the installation fails on Linux if the user installs the Proxy Server as a non-root user and the /var/opt/sun/install directory does not exist.

6353576 

Silent upgrade installation does not work. 

6587776 

Proxy Server from Java ES 5 on Windows XP displays system error 1067. 

6607551 

On Windows, uninstalling the patch does not change the Proxy Server version to the previous version number. 

Reverting the patch through Uninstaller script does not change the service description name to the previous Proxy Server version due to RenameService.exe utility limitations. Therefore, even after uninstalling the patch, the service description shows the latest Proxy version instead of the previous version number.

Internationalization

The following table lists the known issues related to internationalization.

Table 12 Known Issues in Internationalization

ID  

Summary  

6233080 

The Disable Proxying option does not work for the URL with multibyte data (URL encoded) when routing is set through another proxy server. 

6233090 

A URL with multibyte data (URL encoded) cannot be mapped. 

6253844 

Proxy server online help does not support the language zh-cn. 

6297168 

Starting the server in a different system encoding causes any errors returned by the system in that particular system encoding to be logged in the error log. When viewed through the Administration server, the error log might have characters in system encoding that do not display properly. 

Workaround

Change the browser encoding to match the OS locale so that the error log can be properly viewed through the administration interface. But this will be needed every time you move to other pages and then return to View Error Log again. 

6300080 

Proxy server's content rewriting function is inconsistent.  

6526476 and 6526488 

In a standalone installation of proxy server on HP-UX, the installation in GUI mode results in the display of corrupted Japanese characters (ID no. 6526476). If the installation is continued, it results in error while creating an instance (ID no. 6526488).  

Workaround

You can use either of the following workarounds: 

  • Use the CLI mode of installation for Japanese locale on HP-UX.

  • Continue the installation even with the corrupted display of characters. When the installer fails to create an instance, log in to the administration interface and create an instance.

6550995 

The following error message is not localized for all the locales: 

HTTP7774: received extraneous data following response

6600594 

 

SOCKS

The following table lists the known issues related to SOCKS.

Table 13 Known Issues in SOCKS

ID  

Summary  

6245453 

The Quench Updates feature is shown in the GUI and documented for the Server Manager > SOCKS > Configure SOCKS v5 page, but the feature is not implemented. 

6263389 

No error is reported when two instances of SOCKS are started using the same port on Windows. 

6285791 

SOCKS server start command line issue for JavaES 4 is resolved in this release, but existing instances created in JavaES 4 installation will have the problem even after upgrading to the latest 4.0.3 patches. The new instances created after upgrade will not have this problem. This problem is not there in stand-alone installation of web proxy server.