This section lists the more important known issues and limitations at the time of the Sun Java System Web Proxy Server 4.0.3 release. The issues are listed by category:
The following table lists the known issues related to the administration user interface.
Table 6 Known Issues in Administration
ID |
Summary |
6213014 |
RESTART event on Windows is not triggered at the time specified. |
6213017 |
RECONFIG event on Windows is not triggered at the time specified. |
6224535 |
The timeout and retries parameters for the HTTP client cannot be configured through the administration interface. Workaround The default value for the timeout parameter is five minutes and can be overridden by including the parameter, timeout= number of seconds in the http-client-config SAF of the obj.conf file. The default value for the retries parameter is three. The number of request retries can be configured by including the parameter retries=number of retries in the http-client-config SAF of the obj.conf file. The effective timeout is timeout x retries |
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. |
6241978 |
There maybe errors while accessing the administration interface on Windows. Workaround Ensure that the system32 directory on your system contains libnspr4.dll of version 4.5.1 or later else, copy the file from the %install_dir%\bin\proxy\bin directory into the system32 directory and restart the administration server. |
The following table lists the known issues related to caching.
Table 7 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. |
The following table lists the known issues related to documentation.
Table 8 Known Issues in Documentation
ID |
Summary |
6423487 |
The online help page for Monitor Current Activity does not provide details about enabling DNS Statistics. Workaround The following are the steps required to enable DNS Statistics: 1. In magnus.conf file, change DNS to on. 2. Access the Server Manager, and click the Configure DNS Cache link from the Preferences tab. Select the Enable option to enable DNS caching. 3. Add the following line in the obj.cong file- Init cache-size="1024" expire="1200" fn="ip-dns-cache-init" |
The following table lists the known issues related to installation.
Table 9 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. |
6274424 |
In Windows, the value for defaultInstallDirectory in the state file is wrong. The default installation directory in the installer is c:\sun\ProxyServer40, but the statefile generated when you use the command “setup --savestate” does not have c:\sun\ProxyServer40 as the default installation directory. The statefile displays the UNIX template value as the default installation directory. |
6353576 |
Silent upgrade installation does not work. |
The following table lists the known issues related to internationalization.
Table 10 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. |
6233093 |
A filter cannot be created for a URL with multibyte data (URL encoded). |
6233100 |
Multibyte strings from the page being retrieved cannot be rewritten. |
6242032 |
In the Proxy Server 4.0.2 Administration Guide, in Chapter 7, the section “Configuring System Preferences” has wrong description for Parent Array. The correct description is, “A parent array is a proxy array that a proxy or proxy array member routes through”. The issue is fixed only in the English version of the document for the 4.0.3 release. |
6246562 |
Controlling a set of servers installed on different locales and platforms through clusters fails when stopping the set of servers. Workaround Stop each server individually. |
6253844 |
Online Help is not displayed when zh-cn is specified as one of the preferred languages for Simplified Chinese in the browser. Workaround Specify zh-cn as the only preferred language for Simplified Chinese in the browser. |
6255157 |
In the Proxy Server 4.0.2 online help, the link "Upper flame" in the help file for Server-Preferences page opens wrong topic. The issue is fixed only in the English version of the online help for the 4.0.3 release. |
6275141 |
In the Proxy Server 4.0.2 online help, there is a section for Configuring File Cache in the help file that needs to be removed as this feature is removed in the Proxy Server 4.0.3 administration interface. The issue is fixed only in the English version of the online help for the 4.0.3 release. |
6295286 |
In the Proxy Server 4.0.2 Administration Guide, in Chapter 14, the section “Setting up a Reverse Proxy” needs to note in Step 5 that the “/” mapping is added only if the user doesn't change the contents of the “Map Source Prefix” text box provided automatically by the administration interface. The issue is fixed only in the English version of the document for the 4.0.3 release. |
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. |
6300615 |
The meta tag is missing in localized core messages. |
6312044 |
In the Proxy Server 4.0.2 online help, there are references to Cache statistics in the help file for The Monitor Current Activity Page. These references need to be removed as the feature is removed from the Proxy Server 4.0.3 administration interface. The issue is fixed only in the English version of the online help and Administration Guide for the 4.0.3 release. |
6313959 |
In the Proxy Server 4.0.2 Administration Guide, in Chapter 12, the section “To configure the file cache” provides wrong description for step 1. The correct description is, “From the Server Manager, click the Caching tab”. The issue is fixed only in the English version of the document for the 4.0.3 release. |
6313960 |
In the Proxy Server 4.0.2 Administration Guide, in Chapter 12, the section “To create a batch update” includes step 10 that refers to a “Timing section”. This step is an error. The Set Cache Batch Updates page does not have a Timing section. The issue is fixed only in the English version of the document for the 4.0.3 release. |
6316289 |
In the Proxy Server 4.0.2 Administration Guide, in Chapter 12, the section “Building the Cache Directory Structure” includes an example that refers to figure 12-1 instead of 12-2. The issue is fixed only in the English version of the document for the 4.0.3 release. |
6331044 |
In the Proxy Server 4.0.2 Administration Guide, in the preface, the section “Using the Documentation” specfies the location of the Proxy Server 4 documentation. http://docs.sun.com/app/docs/prod/s1.webproxys#hic The section should point to Proxy Server 4.0.2 documentation at: http://docs.sun.com/app/docs/coll/1311.2 The issue is fixed only in the English version of the document for the 4.0.3 release. |
6350957 |
In the Proxy Server 4.0.2 Administration Guide, in Chapter 5, the section “Enabling Security for Listen Sockets” does not mention that security can only be enabled in reverse proxy mode and not in forward proxy mode. Also, in Chapter 8, the section “Specifying Users and Groups” does not mention that security can only be enabled in reverse proxy mode and not in forward proxy mode. The issue is fixed only in the English version of the document for the 4.0.3 release. |
6384616 |
In the Proxy Server 4.0.3 online help, there are formatting errors. The issue is fixed only in the English version of the online help for the 4.0.3 release. |
6387901 |
In the Proxy Server 4.0.2 Administration Guide, Chapter 11, "Proxying and Routing URLs", the section "Chaining Proxy Servers" should mention that you can enter both the servername and the port number in the following format: servername:port in "Route Through Another Proxy" option in the "Set Routing Preferences" page under the Routing tab. The issue is fixed only in the English version of the document for the 4.0.3 release. |
The following table lists the known issues related to monitoring.
Table 11 Known Issues in Migration
ID |
Summary |
||
6412129 |
When a proxy instance is migrated from proxy server 3.6 to proxy server 4.0, the migration tool doesn't modify the setting for Client IP Address Forwarding. In the 4.0 version the Client IP Address Forwarding is set to "Blocked" by default. In the 3.6 version the Client IP Address Forwarding is not set to “Blocked” by default. As a result, the behavior changes because the default value of this feature changes between 3.6 and 4.0. Workaround If the migration tool does not find an entry in the obj.conf file of the migrated instance for the block-ip ObjectType, then add the following line in the obj.conf file. ObjectType fn="block-ip" |
The following table lists the known issues related to monitoring.
Table 12 Known Issues in Monitoring
ID |
Summary |
||
6268536 |
SNMP on Windows does not work if the libnspr4.dll file is not present in the system32 directory. Workaround Ensure that the system32 directory on your system contains libnspr4.dll of version 4.5.1 or later else, copy the file from the %install_dir%\bin\proxy\bin directory into the system32 directory and restart the administration server. |
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 JES4 is resolved in this release, but existing instances created in JES4 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 standalone installation of web proxy server. |