Sun Java System Web Server 6.1 2005Q4 SP5 Release Notes

Known Issues

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

General

The following table lists General known issues.

Table 10 General Known Issues

Problem ID 

Description 

6198559 

JES3: Patch Upgrade of Web Server on Linux throws false `Uninstall' notification. 

Administration

The following table lists the known issues in Administration.

Table 11 Known Issues in Administration

Problem ID 

Description 

6301761 

ACL applet may fail to load with Mozilla 1.4 and Firefox 1.0.6. 

6197731 

Internal Error on accessing Admin Server. 

Workaround: If Web Server 6.1 SP4 is installed on a Windows machine which has Directory Server (versions 5.2 patch 3 or lower) installed, you may run into problems with the Web Server Admin Server. It is advisable to install the Web Server and Directory Server on separate machines to avoid issues. This issue is applicable only on Windows platforms.

6021151 

Problem using HttpServerAdmin to create a JNDI resource containing an LDAP DN 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 

dist-admin: ACL deletion does not clean up obj. 

Workaround: Comment out NameTrans for https-admserv:


#NameTrans fn="assign-name" name="https-admserv" from="/https-admserv/*" 

5035129 

Unable to manage DS user/group/ou using WS 6.1 SP2 Admin on RHLAS 3.0 only. 

4650456 

View Access and View Error doesn’t work properly with multi-byte characters. 

4652585 

When distributed Admin is enabled, the local Admin user becomes disabled 

Workaround: Create a user with the default Admin user name within the distributed Admin group.

Note that the newly created LDAP Admin user must have the same password as the Web Server Admin user. 

4725683 

The date stamp in the log filename is not consistent with the date stamp in the log file entries. 

Workaround: If the date in the log filename extension should match the date of the log entries themselves, configure the server to rotate the log files at 23:59, the end of the day.

4761960 

In Version 6.0 SP4, cannot enable distributed Admin 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 instead 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 to the pages in the Admin GUI. 

4888696 

The Add Server page in the Admin 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 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 `superuser'.

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’ve been deleted. 

4911552 

.shtml files are parsed when they shouldn’t be.

This issue pertains to the Parse HTML page on the Content Management tab in the Class Manager. The .shtml files will be parsed even when settings on this page are configured so that they shouldn’t be. For example, if you specify `Yes', with a exec tag and `All HTML files', .shtml files will still also be 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/appserver/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 Admin 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"

4841310 

Cannot 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 instead 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.

4991278 

No Admin GUI feature available to delete JSP ClassCache files. 

6316262 

Admin GUI does not reflect changes made to the accesslog path. 

6316265 

Admin GUI says `Click Apply' for the changes to take affect but there is no `Apply' button for Admin Server. 

Core

The following table lists the known issue in Core.

Table 12 Known Issues in Core

Problem ID 

Description 

6363944 

webservd child process orphaned when Solaris crypto softtoken (libpkcs11.so) is used in S1WS6.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 

On HP-UX: Executing the ./stop script gives an error message and kills the process group.

Documentation and Online Help

The following table lists the known issues in Documentation and Online Help.

Table 13 Known Issues in Documentation

Problem ID 

Description 

6359385 

Administrator's Configuration File Reference should document the magnus.conf variable MaxKeepAliveConnections value range for 64–bit server.

Additional Information: magnus.conf MaxKeepAliveConnections directive values range from 0 - 1048576 for the 64-bit server.

6358849 

Administrator's Configuration File Reference should document the MaxOpenFiles attribute in the nsfc.conf configuration file.

Additional Information: Details of the MaxOpenFiles attribute are as follows:

  • Attribute: MaxOpenFiles

  • Default Value: 1024

  • Description: Limit on the number of cached open file descriptors.

4964908 

No documentation available regarding feature upgrades.  

5065188 

6173274 

Administrator's Guide incorrectly describes a Find menu Passage Search option in the Advanced Search section. This menu option is not available.

6155266 

Administrator's Guide incorrectly describes the config log level.

Correction: The Web Server config level should be defined as follows:

Message indicate a misconfiguration.

6206074 

Administrator's Configuration File Reference describes an incorrect default value for the ChildRestartCallback directive.

Correction: The default value is no directive.

6170766 

Installation and Migration Guide describes an incorrect method of upgrading a newer version of Web Server in the Before You Install Sun One Web Server section.

Correction: To upgrade Sun One Web Server 6.1, which is a part of the Sun Java Enterprise System 1, users must use patchadd.

6170769 

Administrator's Configuration File Reference has incorrect information about the AdminLanguage directive.

Correction: The AdminLanguage directive is only applicable to the language displayed in the log messages and not the GUI.

6173273 

Administrator's Guide has a typo error under section Choosing MIME Types.

Correction: The sentence should be read as follows: For more information, see the MIME Types page in the online help and Using Virtual Servers.

6173133 

NSAPI Programmer's Guide describes an incorrect example of a NSAPI Function Reference.

Correction: The example should be read as follows:

FilterMethods methods = FILTER_METHOD_INITIALIZED;

6173272 

Administrator's Guide incorrectly documents the supported version of Java as `1.4.1_03'.

Correction: Sun Java System Web Server supports Java 2 Platform, Standard Edition (J2SE) 1.4.2_04 and greater (32-bit only; 64-bit is not supported). J2SE software is bundled with the Web Server and installed during installation, if you choose to install it.

You can also install your own JDK at a later time, following installation of the Web Server. If you plan to use the Administration server, a JDK must be installed.  

5016571 

Online Help page under Generic Thread Pools gives invalid information.

5029460 

Administrator's Guide documents an incorrect certmap.conf configuration.

The description of certmap.conf in the guide contains the following text:

The first line specifies a name for the entry and the attributes that form the distinguished name found in the CA certificate. The name is arbitrary; you can define it to be whatever you want. However, issuerDN must exactly match the issuer DN of the CA who issued the client certificate. For example, the following two issuerDN lines differ only in the spaces separating the attributes, but the server treats these two entries as different:  

certmap sun1 ou=Sun Certificate Authority,o=Sun, c=UScertmap sun2 ou=Sun Certificate Authority,o=Sun, c=US

Correction: The two lines should be read as follows:

certmap sun1 ou=Sun Certificate Authority,o=Sun, c=UScertmap sun2 ou=Sun Certificate Authority, o=Sun, c=US

5031366 

Invalid links in the online version of Administrator's Guide

4968568 

Administrator's Configuration File Reference guide's description on the ConnQueueSize directive is not clear.

4975161 

Administrator's Configuration File Reference does not document the optional parameter `block-size' for pool-init.

5002190 

Administrator's Guide doesn't contain information about the htpasswd command utility.

Additional Information: The htpasswd command is used to generate or modify a password file suitable for use with the htaccess access control mechanism.

htpasswd Usage:

htpasswd [-c] passwordfile username [password]

-c creates a new password file.  

As noted, -c creates a new password file by overwriting an old one if it already exists. Without -c, the command will modify the existing file by either updating the user's password (if user already exists) or adding a new user with the given name.

If the optional password argument is not given, it will prompt interactively for the password to assign.  

Note that htaccess is not the preferred access control mechanism in Web Server. Wherever possible, use ACLs instead. 

5002192 

Administrator's Configuration File Reference has incorrect information about the loglevel attribute.

Correction: The loglevel description should be read as follows:

Controls the default type of messages logged by other elements to the error log. Allowed values are as follows, from highest to lowest: finest, finer, fine, info, warning, failure, config, security, and catastrophe. 

5020640 

NSAPI Programmer's Guide does not document the %duration% flex-log format variable.

5029321 

Administrator's Configuration File Reference documents the <Client uri="*foo*" uri="*~bar*"> directive incorrectly.

Correction: In some cases the evaluation can be rewritten to occupy a single evaluation statement:

<Client uri="*foo*~*bar*">.

It is functionally the same as  

<Client uri="*foo*" uri="~*bar*">.

5038534 

Administrator's Configuration File Reference has incorrect default value for the LogFlushInterval directive.

Correction: The correct default value for the LogFlushInterval directive is 2 seconds.

5043491 

Incorrect online help content. 

4781137 

Administrator's Guide has the following incorrect information:

  • The path where libdigest-plugin.ldif exist is not defined in the guide.

    Additional Information:libdigest-plugin.ldif is available at <server-root>/plugins/digest/libdigest-plugin.ldif.

  • Information to configure the Web Server to process digest authentication (set the digestauth property of the database definition in dbswitch.conf) is given without describing the procedure to do it.

  • libdigest-plugin.so is incorrectly mentioned as libdigest-plugin.lib.

  • Description of iplanetReversiblePassword is missing.

4823362 

Administrator's Guide needs to be updated with additional information regarding ACL.

Additional Information: If there are more than one ACLs that match, the server uses the last statement that matches. The default ACL is bypassed as the uri ACL is the last statement that matches.

4862795 

Administrator's Guide's description on the Archive Log File page is not clear.

Correction: The following note to be added to the document to make the description more clear: The user can archive or delete the old log files (this activity is not done by the Web Server).

5046588 

Installation and Migration Guide incorrectly documents the supported version of Sun accelerator hardware.

Correction: The supported version of Sun accelerator hardware is 500 and 1000.

5052605 

The NSAPI Programmer's Guide does not clearly specify that content-type needs to be in lower case.

5053339 

Online Help — Directory Indexing information is missing in Administrator's Guide and online help.

5062560 

Installation and Migration Guide does not document the method of disabling the start-on-boot option.

Additional Information: Users can disable the start-on-boot option as follows:

On Solaris and HPUX — Turn off by editing the S1WS_START_ONBOOT variable in the webserver01 script.

[Solaris] 

/etc/init.d/webserver01

[HPUX] 

/sbin/init.d/webserver01

On Linux — Delete the following links to disable it: 

/etc/rc.d/rc3.d/S75webserver01

/etc/rc.d/rc5.d/S75webserver01

6067059 

In Administrator's Guide any tags without content body should have `/' before the end `>' tag.

4928287 

All documents do not inform user the nonexistence of <instance>/lib directory.

Additional Information:This directory is not created by the installer. Users have to create the directory if it does not exist.

4970961 

Administrator's Configuration File Reference doesn't explain ChunkedRequestTimeout in detail.

6308091 

Administrator's Configuration File Reference — Wildcard pattern with tilde in ppath doesn't work as documented.

Correction: Users have to configure either of the followings:

Config 1

<Object ppath="*~*.gif*">AddLog fn=flex-log name="access"</Object>

Config 2

<Object ppath="*~*(.gif|.gif/)">AddLog fn=flex-log name="access" </Object>

6285234 

Administrator's Configuration File Reference incorrectly describes the default value of the StrictHttpHeaders directive as on.

Correction: The default value of the StrictHttpHeaders directive is off.

6067318 

Administrator's Configuration File Reference has insufficient information about the set-variable error parameter.

Correction: The description of the set-variable error parameter should be read as follows:

Sets the HTTP status code and aborts the request by returning REQ_ABORTED. To set the HTTP status code without aborting the request, use the set-variable error parameter along with the noaction parameter.

To rewrite an HTTP status code, use a <Client> tag to match the original status code and an Output directive to set the new status code. For example, the following would rewrite all 302 Moved Temporarily responses to 301 Moved Permanently responses: 

<Client code="302">Output fn="set-variable" error="301 Moved Permanently" noaction="true"</Client>

6281323 

Release Notes for Sun Java System Web Server 6.1 2005Q1 SP4 documents the incorrect version of Windows 2003 operating system.

Correction: The supported version of Windows 2003 for Web Server 6.1 SP4 is

Windows Server 2003, SP1 Enterprise Edition

6237209 

Release Notes for Sun Java System Web Server 6.1 2004Q3 SP3 doesn't include complete information regarding various RedHat Linux kernels.

6237303 

Release Notes for SUN ONE Web Server 6.1 does not list all patches that are required for Solaris SPARC.

Additional Information: 109326-09 is a required patch for Web Server 6.1 on Solaris 8.

6230379 

Administrator's Configuration File Reference incorrectly describes a remove-file() SAF.

Correction: The remove-file() is renamed to delete-file().

6208955 

NSAPI Programmer's Guide incorrectly documents the description of SERVER_SOFTWARE as MAGNUS_VERSION_STRING.

Correction: The NSAPI variable for SERVER_SOFTWARE is system_version().

4673436 

To have iWS recognize remote shares within Domain Controller environment. 

4841310 

Can't get REMOTE_USER variable when authenticated by .htaccess.

5059527 

Web Server configuration files and scripts are writable by webservd. 

6320016 

Administrator's Configuration File Reference doesn't clearly define the default value of listenQ on Windows.

Correction: The default value of listenQ on Windows is 200.

Installation

The following table lists the known issues in Installation.

Table 14 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 61SP2 core is also installed along with, or prior to installing JDK alone. In addition, if 61SP2 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

Migration

The following table lists the known issues in Migration.

Table 15 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:


NameTrans fn=document-root root="<existing_doc_root>"

to 


NameTrans fn=document-root root="$docroot"

In server.xml under the relevant VSCLASS change the line:


<PROPERTY name="docroot" value="<existing_doc_root>"/>

to 


<PROPERTY name="docroot" value="<new_doc_root>"/>

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 please refer to the JES 3 Migration and Upgrade guide.

Samples

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 16 Known Issues in Samples

Problem ID 

Description 

5014039 

Simple JSPs throw exception due to <distributable> tag in web.xml 

Workaround: Remove the tag <distributable></distributable> from the web.xml under the simple/src directory. Redeploy the web-app.

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. 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"/>

Search

The following table lists the known issues in Search.

Table 17 Known Issues in Search

Problem ID 

Description 

4977315 

5038203 

AIX-Search Engine of 6.1 should have the ability to change the sort order. 

Workaround: For changing default order add `+' as a first character of the sort string. Since `+' in uri is escaped use `%2B' to change the order. In this case change the URL to: http://host/search/index.jsp?si=1&ns;=10&c;=test&qt;=*&sb;=%2Bwriter.

4684124 

If the docroot of an already indexed collection is changed, the document returned by the search throws a ‘Document Not Found’ error. 

Workaround: Rebuild the entire collection.

To do so: 

  • Remove all documents and add them back again.

    Or

  • Delete the collection and create it again.

4911725 

Search doesn’t work when you search for a word using a different case pattern. 

Search results will not be displayed on the search page if you search using a word of mixed case (for example, typing jaVa instead of java or JAVA). 

4963236 

On HP-UX: PDF files are not converted to HTML for inclusion in search collections. 

This occurs if the following patch is installed on the HP-UX 11i system: 

PHSS_28871 — ld/linker cumulative patch 

Security

The following table lists the known issues in Security.

Table 18 Known Issues in Security

Problem ID 

Description 

4898077 

Enable SSL, inconsistent behavior between HttpServerAdmin and iWS console. 

Workaround: Use the following Syntax:

HttpServerAdmin create -l -id <id> -ip <ip> -port <port> -sname serverName -defaultvs <defaultvs> [-cert <certificate name>] [-sec <on|off>] [-acct <#accthreads>] -d server_root -sinst http_instance

Note: Do not use `true|false' or `1|0' or `yes|no' for the -sec option, use `on|off' instead. 

4671445 

Sun Java System Web Server cannot connect to an LDAP server over SSL if LDAP client authentication is required. 

If Sun Java System Web Server contacts an LDAP server that requires client authentication (in this case, the Web Server is the client), the Web Server’s certificate cannot be sent and access will fail. 

4863599 

Cannot use the same group name under different organizational units. 

If the same group name is used, and you try to restrict access with the group name, Sun Java System Web Server returns an error when clients try to access the site. 

Workaround: Use a different group name for each organizational unit.

4963468 

In some circumstances, the `list' right has no effect on directory listing. 

According to Chapter 9 of the Sun Java System Web Server 6.1 Administrator’s Guide, the `list' right is required to obtain directory listings from directories that do not contain an index file. However, in certain circumstances it is possible to obtain a directory listing, even if the applicable ACLs deny the list right. For this reason, if you need to restrict directory indexing, it is recommended that you do so by disabling indexing, as discussed in Chapter 16 of the Sun Java System Web Server 6.1 Administrator’s Guide, instead of (or in addition to) denying the list right.

6310956 

6298215 

When LDAP drops the connection because of inactivity (for example, timeout set on the LDAP), Web Server is unable to re-initialize the connection to LDAP. This only occurs when Web Server is installed as part of the JES3/JES4 install, the problem is not present with standalone (file-based) installation.  

Workaround:

  1. Copy the library libldap50.so from the file-based install of Web Server and paste it to the following location in your current setup: /opt/SUNWwbsvr/bin/https/lib

  2. Restart the Web Server.

Tools

The following table lists the known issues in Tools.

Table 19 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 the deploy, and only if it succeeds.

Workaround: The error seems to occur when wdeploy reads the stdout/stderr after execution of the reconfigure script following the deploy. 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.

Web Container

The following table lists the known issues in the Web Container.

Table 20 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 may lead to unexpected behavior for Windows users (for example, if a client makes a request for index.HTML, expecting this to match index.html).

WebDAV

The following table lists the known issues in WebDAV.

Table 21 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.