This section lists the more important known issues and limitations at the time of the Sun Java System Web Server 6.1 SP6 release. The issues are listed as follows:
The following table lists General known issues.
Table 12 General Known Issues
Problem ID |
Description |
---|---|
6198559 |
JES3: Patch upgrade of Web Server on Linux displays false `uninstall' notification. |
4988370 6413819 |
Contents does not get updated under a particular situation on HP-UX 11.0 platforms. HP-UX operating system has two cache spaces called Page Cache and Buffer Cache for accessing files. Normally, when the application performs the mmap function, the file is mapped to Page Cache. However, currently the operating system has no responsibility to synchronize the data between the Page Cache and Buffer Cache, if the mmap is performed as PRIVATE option. Even if you copy the file, the operating system refreshes the cached data only in the Buffer Cache. Workaround: Use the vi editor to update the contents each time. |
6404983 |
Searching of Users and Groups through LDAP server using Administration Graphical User Interface fails. Workaround: For this feature to work, install Red Hat Linux AS 3.0 update 1 — uname -r: 2.4.21-9.ELsmp. |
The following table lists the known issues in Administration.
Table 13 Known Issues in Administration
Problem ID |
Description |
|
---|---|---|
6301761 |
ACL applet might fail to load with Mozilla 1.4 and Firefox 1.0.6. |
|
6021151 |
Problem using HttpServerAdmin to create a JNDI resource containing an LDAP domain name containing commas. Workaround: For HttpServerAdmin to escape the `,' in the property use `\\' as escape character (and use `\' in Windows platforms). In the property java.naming.provider.url=ldap://localhost:389/ou=loggingQueues,ou=tms,ou=services,ou=abc the `,' are escaped as shown here: -property java.naming.provider.url=ldap://localhost:389/ou=loggingQueues\\,ou=tms\\,ou=services\\,ou=abc |
|
5007892 |
Distributed Administration: ACL deletion does not clean up obj.conf. Workaround: Comment out NameTrans for https-admserv:
|
|
5035129 |
Unable to manage Directory Server user/group/ou using Web Server 6.1 SP2 Administration on RHLAS 3.0. |
|
4650456 |
View Access and View Error doesn’t work properly with multi-byte characters. |
|
4652585 |
When Distributed Administration is enabled, the local Administration user is disabled Workaround: Create a user with the default Administration user name within the distributed Administration group. Note that the newly created LDAP Administration user must have the same password as the Web Server Administration user. |
|
4725683 |
The log file date stamp does not take the local time zone into account and shows the incorrect date. Workaround: If the date in the log file filename extension should match the date of the log entries, configure the server to rotate the log files at 23:59. |
|
4761960 |
Web Server 6.0 SP4: Cannot enable distributed Administration when using SASL and anonymous bind. Workaround: Do not use anonymous bind to SSL enabled directory server. |
|
4841310 |
Can't get REMOTE_USER variable when authenticated by .htaccess. Workaround: If you enable .htaccess files, the server checks for .htaccess files before serving resources. The server looks for .htaccess files in the same directory as the resource and in that directory's parent directories, up to and including the document root. For example, if the Primary Document Directory is set to /sun/server/docs and a client requests /sun/server/docs/reports/index.html, the server will check for .htaccess files at /sun/server/docs/reports/.htaccess and /sun/server/docs/.htaccess. Note that the server's Additional Document Directories and CGI Directory functionality allows an administrator to define alternate document roots. The existence of alternate document roots affects .htaccess file processing. For example, consider a server with the Primary Document Directory set to /sun/server/docs and a CGI program at /sun/server/docs/cgi-bin/program.cgi. If you enable CGI as a File Type, the server will evaluate the contents of both /sun/server/docs/.htaccess and /sun/server/docs/cgi-bin/.htaccess when a client issues a request for the CGI program. However, if you configure a CGI Directory at /sun/server/docs/cgi-bin, the server will inspect /sun/server/docs/cgi-bin/.htaccess but not /sun/server/docs/.htaccess. This occurs because specifying /sun/server/docs/cgi-bin as a CGI Directory marks it as an alternate document root. |
|
4865295 |
The End User Administration feature (under Distributed Administration in the Administration interface) is no longer supported. |
|
4882999 |
Inconsistent look and feel of the Administration GUI. |
|
4888696 |
The Add Server page in the Administration GUI disappears in Netscape 7.0 when insufficient information is entered. Workaround: Enter complete information on the Add Server page before clicking OK. If necessary, reload the page to restore the Add Server GUI, or click another page or another tab and then navigate back to the Add Server page. This problem occurs only in Netscape 7.0. |
|
4910309 |
The word `null' is incorrectly displayed on an alert message. This word displays when editing directory services in the Pick Directory for Virtual Server page in the Virtual Server Manager. |
|
4905808 |
Super users cannot access the Administration interface after enabling distributed administration. Workaround: After enabling distributed administration, create a user in LDAP with the same administration user name and password as that of super user. |
|
4908694 |
Default link not working for Logging Settings. The default link on the Logging Settings for Virtual Server page does not set the default path, but rather acts as a reset button. |
|
4910197 |
When editing a JDBC resource, the properties page retains values after they have been deleted. |
|
4911552 |
.shtml files are parsed even if you configure them to be un-parsed. |
|
No ID |
The sun-web.xml file bundled with the Web Server points to the wrong DTD location. Correction: The correct location is http://www.sun.com/software/dtd/webserver/sun-web-app_2_3-1.dtd. |
|
6284698 |
Web Server not operational when installed as non root user. Workaround: Start the Web Server instance from the command line instead of using the Web Administration console. |
|
6078104 |
JSP applications are not accessible from WS6.1 when passthrough plug-in is configured. Workaround: Change the line from the service directive of passthrough: From: Service type="magnus-internal/passthrough" fn="service-passthrough"servers="http://server:port" To: Service fn="service-passthrough" servers="http://server:port" |
|
4991278 |
No Administration GUI feature available to delete JSP ClassCache files. |
|
6316265 |
Administration GUI says Click Applyfor the changes to take affect but there is no Apply button for Administration Server. |
The following table lists the known issue in Core.
Table 14 Known Issues in Core
Problem ID |
Description |
---|---|
6363944 |
webservd child process orphaned when Solaris crypto softtoken (libpkcs11.so) is used in Web Server 6.1SP5 64-bit. Workaround: This problem occurs only when the server is explicitly configured to use the Solaris softtoken. If you have to use fork(), Runtime.exec(), or <!--#exec cmd="..."-->, do not configure the server to use the Solaris softtoken. |
6313832 |
Existing 32-bit plug-ins cannot be used with the 64-bit release. Attempting to load a 32-bit plug-in using the 64-bit Sun Java System Web Server release will result in an error message such as the following: Sun ONE Web Server 6.1SP5 (64-Bit) B10/28/2005 09:00 failure: CORE3170: Configuration initialization failed: Error running init function load-modules: dlopen of plugin.so failed (ld.so.1: webservd: fatal: plugin.so: wrong ELF class: ELFCLASS32) Workaround: Use the 32-bit release of Sun Java System Web Server or contact the plug-in vendor to obtain a 64-bit release of the affected plug-in. |
4939491 |
HP-UX: Executing the ./stop script gives an error message and kills the process group. |
The following table lists the known issues in Documentation and Online Help.
For a list of known issues in the localized versions of 6.1 documentation, see Issues Resolved in 6.1 SP6 Documentation.
The following table lists the known issues in Installation.
Table 16 Known Issues in Installation
Problem ID |
Description |
---|---|
5020317 |
JDK only upgrade results in disabling search (user receives an exception, and search page will not be accessible from GUI). Workaround: This exception does not happen if Web Server 6.1 SP2 core is also 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. |
4855263 |
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 no install the Web Server into a directory with spaces in the name. |
4869238 |
On Windows, the Sun Java System Web Server installer will not take 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 dialog allows you to enter up to 256 characters). |
4901205 |
On Solaris, ctrl+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. |
4937915 |
On AIX: ctrl-c makes the terminal screen hang during installation. This occurs on the computer name screen (the screen used to specify the name of the computer on which the Web Server will be installed). |
4960048 |
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: $server-root/plugins/snmp/ magt/CONFIG $server-root/plugins/snmp/ sagt/CONFIG |
The following table lists the known issues in Migration.
Table 17 Known Issues in Migration
Problem ID |
Description |
||||
---|---|---|---|---|---|
4790457 |
Can't change the document root of migrated server from 4.1. Workaround: Edit the migrated instance's obj.conf and server.xml manually. These files are located under <code><SERVER_ROOT>/<HTTPS-INSTANCE>/config directory. In obj.conf change the line:
to
In server.xml under the relevant VSCLASS change the line:
to
|
||||
6213097 |
ktsearch.jar is not getting migrated correctly on Sun Java Enterprise System 3 (JES3). Workaround: Manually edit the server.xml file of the migrated instance to point to the correct path. For Linux: /opt/sun/private/share/lib/ktsearch.jar For Solaris Sparc: /usr/share/lib/ktsearch.jar |
||||
5007081 |
Web-apps file status ignored during migration from 6.0 to 6.1 Web-apps status defined at the file level in the server.xml file is not getting migrated. If a user has switched off the status of the web-apps file to suppress them, upon migration these web-apps are exposed. Workaround: Edit the server.xml file of the migrated instance and turn off status for each web-app. |
||||
4988156 |
Installation of SP_2 patch on existing install (update) If you wish to upgrade the Sun Java System Web Server 6.1 that is installed as a part of Sun Java Enterprise System (JES), to the latest Service Pack, you will have to download and apply the relevant patches. For more details refer to the JES 3 Migration and Upgrade Guide. |
The following table lists the known issues in the sample applications. Note that none of these issues prevent the sample applications from functioning correctly.
Table 18 Known Issues in Samples
Problem ID |
Description |
---|---|
5014039 |
Simple JSPs throw exception due to distributable tag in web.xml Workaround:
|
No ID |
rmi-iiop sample is missing a step. In the Deploying the Sample Application section, after executing the command ant deploy (step 2), restart the Web Server instance. Note – ant is a Java-based build tool and must be downloaded from Apache at http://ant.apache.org Note: . Also see the information provided in <install_root>/plugins/java/samples/docs/ant.html. |
No ID |
jdbcrealm sample has the wrong Oracle driver name. In the `Compiling and Assembling the Sample Application' section, step 2b, change the following line from this: <PROPERTY name="dbdrivername" value="oracle.jdbc.pool.OracleDataSource"> To this: <PROPERTY name="dbdrivername" value="oracle.jdbc.driver.OracleDriver"> |
The following table lists the known issues in Search.
Table 19 Known Issues in Search
The following table lists the known issues in Security.
Table 20 Known Issues in Security
The following table lists the known issues in Tools.
Table 21 Known Issues in Tools
Problem ID |
Description |
---|---|
4905696 |
On Windows, deployment fails if the class file depth (along with the file name) exceeds 255 characters. |
4912181 |
On Linux, a null pointer exception is thrown when deploying an application using the wdeploy command-line utility. This happens at the end of deployment, and only if it succeeds. Workaround: The error occurs when wdeploy reads the stdout/stderr after executing reconfigure script following deployment. The reconfigure should go through, but you should check to see if the server did indeed reconfigure by looking in the errors log for the reconfigure message. If the message is not there, then run the reconfigure script manually. |
The following table lists the known issues in the Web Container.
Table 22 Known Issues in the Web Container
Problem ID |
Description |
---|---|
4903162 |
Issue on Windows related to the case of url-patterns. Per the Servlet specification, url-pattern elements in web.xml are treated in a case sensitive manner. This might lead to unexpected behavior for Windows users (for example, if a client makes a request for index.HTML, expecting this to match index.html). |
The following table lists the known issues in WebDAV.
Table 23 Known Issues in WebDAV
Problem ID |
Description |
---|---|
4892017 |
Unable to rename or move a resource if the parent directory is locked exclusively. This occurs when DAV clients send the incorrect If : header. For example, if you connect to the Web Server using Macromedia® Dreamweaver® or DAV Explorer, create a collection, and then lock the collection with depth infinity (which locks all of its resources as well), you will not be able to rename or move a resource. Adobe® GoLive® sends the correct If : header only if the lock’s owner href matches auth_user. In all other cases with GoLive, the wrong header will also be sent. |
4902651 |
Lock Management screen in the Virtual Server Manager does not display the lock information properly for hard links. Symbolic links (hard and soft) are not supported by the WebDAV implementation in Sun Java System Web Server. |
The following table lists the known issues in the localization.
Table 24 Known Issues in the Localization
Problem ID |
Description |
---|---|
4937055 |
The Administration Online Help of Web Server are not localized. The Administration online help has been localized only up to the 1st level. The initial help pages are localized but clicking the links on a page (for example, Removing a Server) displays help content in English language. |
6441984 |
The Administration Online Help is displayed in English even if the locale is set to zh-cn. For zh-cn locale, the Administration GUI Online Help is in English. If the browser locale is zh-cn, then the complete Administration GUI Online Help is displayed in English language. |
6315783 |
If the browser locale is French (fr), links to Online Help on the Search page leads to English documents though localized pages are available. Workaround: Modify the help URL by adding fr/ before the filename as follows: http://<host>:<port>/search/help/fr/basic-search.html. |