These release notes contain important information available at the time of the release of the Sun JavaTMSystem Web Proxy Server 4.0.2 product, hereafter referred to as Proxy Server 4.0.2. Platform summary and known problems are addressed here. Please read this document and associated documents before you begin using the Sun product.
This document contains the following sections:
The following enhancement has been made in Proxy Server 4.0.2:
Proxy Server 4.0.2 installer supports the upgrade of an existing Proxy Server 4.0 installation to 4.0.2. For the Java Enterprise System installations of Proxy Server 4.0.1, you need to install the patches that correspond to the 4.0.2 release.
This section provides information about supported platform components for Proxy Server 4.0.2
This section includes the following topics:
The following table summarizes the Proxy Server 4.0.2 platform requirements.
Table 1 Platform Requirements for Proxy Server 4.0.2
Operating System |
Minimum Memory |
Recommended Memory |
Recommended Disk Space* |
Sun Solaris™ 8 for SPARC® |
256 MB |
512 MB or higher |
512 MB or higher |
Sun Solaris 9 for SPARC |
256 MB |
512 MB or higher |
512 MB or higher |
Sun Solaris 10 for SPARC |
256 MB |
512 MB or higher |
512 MB or higher |
Sun Solaris 9 for x86 |
256 MB |
512 MB or higher |
512 MB or higher |
Sun Solaris 10 for AMD Opteron™ |
256 MB |
512 MB or higher |
512 MB or higher |
Red Hat Linux Advanced Server 2.1** |
256 MB |
512 MB or higher |
512 MB or higher |
Red Hat Linux Advanced Server 3 Update 4 |
256 MB |
512 MB or higher |
512 MB or higher |
Microsoft Windows 2000 Server Service Pack 4 |
256 MB |
512 MB or higher |
512 MB or higher |
Microsoft Windows 2000 Advanced Server |
256 MB |
512 MB or higher |
512 MB or higher |
Microsoft Windows 2003 Enterprise Edition |
256 MB |
512 MB or higher |
512 MB or higher |
* Depends on cache capacity setting. The default cache capacity setting is 2GB.
** Support for the following Red Hat Linux operating system is now listed as Deprecated and will be removed with the “next” release of the Sun Java System Web Proxy Server product :
Red Hat Linux Advanced Server 2.1
Please take needed action to move or migrate your Web Proxy Servers to a supported operating system.
The following table lists the browsers that are supported with Proxy Server 4.0.2.
Table 2 Supported Browsers for Proxy Server 4.0.2
Browser |
Version |
Microsoft Internet Explorer |
6.0 |
Netscape™ |
7.1, 7.2 |
Mozilla™ |
1.4.1, 1.7.2 |
Your browser needs to have Java enabled.
In addition to the UNIX operating system memory and disk space requirements listed in Platform Requirements, your system must also have adequate swap space:
Solaris requires swap space at least as large as the amount of RAM on your system (twice the amount of RAM is recommended)
Linux requires 256 MB swap space
The Sun Java System Web Proxy Server 4.0.2 documentation is provided in a number of ways:
Manuals—You can view the Proxy Server 4.0.2 manuals and release notes in HTML and in printable PDF formats.
Online help—Click the Help button in the graphical interface to launch a context-sensitive help window.
To obtain accessibility features that have been released since the publishing of this media, consult Section 508 product assessments available from Sun upon request to determine which versions are best suited for deploying accessible solutions. Updated versions of applications can be found at: http://sun.com/software/javaenterprisesystem/get.html.
For information on Sun’s commitment to accessibility, visit http://sun.com/access.
This section lists the most important issues fixed in the following releases:
The following table lists the issues resolved in Sun Java System Web Proxy Server 4.0.2
Table 3 Issues Resolved in Sun Java System Web Proxy Server 4.0.2
ID |
Summary |
5097664 |
ssl-tunnel-timeout parameter does not work on Windows. |
6225025 |
ftp-listing-width parameter does not work correctly. |
6251805 |
Changes to archive logs results in a crash. |
6262277 |
Changing the minimum timeout value for ICP from 400 to 50. |
6292690 |
In Proxy Server 4, while using IE 6.0 to access the administration interface, can not select the original partition using Manage Sections>Partition . |
6292786 |
Proxy Server does not write transfer time (and other times) to access log. |
6308714 |
Proxy Server fails to start if umask is not set to 022. |
6310909 |
In Proxy Server 4.0.1 point product, version string of the product name was over translated for French locale from 2005Q3 to 2005T3. |
6310910 |
In Proxy Server 4.0.1 point product, many missing apostrophes in installer messages on French locale. |
6310944 |
In Proxy Server 4.0.1 point product, CLI installer fails to display the license. |
6310961 |
In Proxy Server 4.0.1 point product, the “Yes” in the license installer screen on Spanish locale not localized. |
6312723 |
Cannot access SSL sites with IP address while using Proxy Server 4.0. |
6313981 |
In Proxy Server 4, not able to change the value of Rewrite Content Location and Rewrite Headername after creating a new Reverse Mapping using the administration interface. |
6315817 |
Multiple simultaneous CONNECT (SSL Tunneling) requests cause thread starvation. |
6330348 |
High Memory usage by proxy process in solaris 10 during stress run. |
6333995 |
Memory leak while running stress tests for CONNECT. |
6335919 |
Proxy Server's FTP client does not close a connection when the FTP Server has closed. |
6335922 |
Proxy Server FTP client does not send USER request to FTP Server. |
6336550 |
Error when trying to install Proxy Server 4.0.1 into a directory that contains a Proxy Server 4.0 install. |
The following table lists the issues resolved in Sun Java System Web Proxy Server 4.0.1.
Table 4 Issues Resolved in Sun Java System Web Proxy Server 4.0.1
ID |
Summary |
2126143 |
The same regular expression does not work in URL Filters, but works in Access Control and Routing. |
2126380 |
Memory leak in the ICP process of the proxy server. |
6231283 |
The administration server on Linux Red Hat Advanced Server 3.0, fails to startup. |
6237346 |
The flexanlg utility dumps core while generating a log analysis report using the Extended2 log file format. |
6240767 |
The add/edit listen sockets for the administration server and the proxy server instance do not verify for used ports. |
6242627 |
Localized core messages are not getting displayed. |
6243369 |
Entry of multi-byte characters in the pages related to SOCKS need to be prevented. |
6244103 |
Internal server error is displayed when the Set Connectivity Mode page of the proxy server instances is accessed on a Linux Advanced Server 3.0, Korean locale. |
6245408 |
An internal error is displayed when a newly added partition is accessed if the administration user and the proxy instance user are different. |
6249166 |
Inconsistency in the display of the Control Cluster, Modify Server, and Remove Server pages in the Cluster tab when the host name in the URL is replaced with localhost while accessing the proxy server. |
6253014 |
Crash occurs in the init-proxy SAF when there are more than 9 NameTrans directives in the obj.conf file on Linux Red Hat Advanced Server 3.0. |
6254508 |
The batch update command exits with segmentation fault. |
6255214 |
Cannot edit or remove an entry in the content URL rewriting page consisting of multibyte characters. |
6255216 |
Some LDAP entries in the socks5.conf lead to socksd crash. |
6259314 |
Some of the localized online help pages are not synchronized with the English online help pages. |
6261440 |
Duplicate English online help exists in the installation directory. |
6263694 |
Online Help unavailable for the Add and Replace Compromised Key List and Certificate Revocation List pages. |
6263721 |
The wrong help page is displayed for the Add/Replace Cert pages in the Server Manager. |
6274186 |
Unable to delete a server instance. |
6276398 |
Remove the localized online help from the base workspace. |
6285078 |
Entry for authentication failure of SOCKS request missing from log files. |
6285779 |
Unable to start the proxy server instance if the serverID has a white space. |
6285788 |
SOCKS server crashes when authentication is used. |
6289242 |
HTTP smuggling in Proxy Server 4. |
6293449 |
Proxy Server 4 does not close the connection immediately with the CONNECT method. |
6296169 |
The header Cache-last-checked is broken in Proxy Server 4 installed on other locales. |
6296225 |
The Proxy Server instance may intermittently crash when DNS caching is enabled. |
6301786 |
Localized Core Message not getting displayed on Solaris 9X86, Linux AS 3.0. |
6311463 |
On the proxy process, the number of open file descriptors keeps increasing with time, resulting in the proxy running out of file descriptors and dropping connections. |
This section lists the more important known issues and limitations at the time of the Sun Java System Web Proxy Server 4.0.2 release. The issues are listed by category:
The following table lists the known issues related to the administration user interface.
Table 5 Known Issues in Administration
ID |
Summary |
6213012 |
ROTATELOGS event on Windows is not triggered at the time specified. |
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. |
6303619 |
An ACL with a database that is registered with a name other than default does not work properly. Workaround Add a new element, USERDB id=xyz in the proxy server instance server.xml file. |
6328678 |
Cannot set ICPtimeout value to less than 400 milli seconds through the administration interface. Workaround Edit the icp.conf file of the proxy instance to change the value of the timeout parameter. |
The following table lists the known issues related to caching.
Table 6 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. |
6275141 |
The File Cache feature is shown in the GUI and documented for the Server Manager > Caching > Configure File Cache page, but the feature is not implemented. |
6289188 |
When you install proxy server 4.0 as non-root user and administration server as root user, any changes you make to the cache settings in the administration user interface result in the permissions for cache file and cache directory changing from non-root to root. Workaround After changing the cache settings in the administration user interface, login to the machine and apply chown -R command on the proxy cache directory. |
The following table lists the known issues related to documentaion.
Table 7 Known Issue in Documentation
ID |
Summary |
||
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”. |
||
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. |
||
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. |
||
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 |
||
6331050 |
In the Proxy Server 4.0.1 Administration Guide, in Chapter 1, the section “New in This Release” specfies the location of the Proxy Server 4 Release Notes. http://docs.sun.com/app/docs/prod/s1.webproxys#hic The section should point to Proxy Server 4.0.2 Release Notes at : http://docs.sun.com/app/docs/coll/1311.2 |
||
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. |
||
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 GUI. |
The following table lists the known issues related to installation.
Table 8 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. |
The following table lists the known issues related to internationalization.
Table 9 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. |
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. |
6300615 |
The meta tag is missing in localized core messages. |
The following table lists the known issues related to monitoring.
Table 10 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 11 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 |
Cannot start SOCKS process by using command line. Workaround Use administration GUI for starting SOCKS server. Or, set LD_LIBRARY_PATH with the required shared component locations. For example, export LIBRARY_PATH=/usr/lib/lwp:/usr/lib/mps/secv1:/usr/lib/mps:/usr/lib/mps/sasl2:/opt/sun/private/lib:/opt/sun/private/share/lib:/opt/sun/lib:$LD_LIBRARY_PATH |
If you have problems with Sun Java System Web Proxy Server 4.0.1, contact Sun customer support using one of the following mechanisms:
Sun Software Support services online at
The telephone dispatch number associated with your maintenance contract
Please include the following information:
Description of the problem, including the situation where the problem occurs and its impact on your operation
Machine type, operating system version, and product version, including any patches and other software that might be affecting the problem
Detailed steps on the methods you have used to reproduce the problem
Any error logs or core dumps
Sun is interested in improving its documentation and welcomes your comments and suggestions. You can submit your comments by going to: http://docs.sun.com/app/docs/form/comments