Sun Java System Web Server 6.1 SP10 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 SP10 release. The issues are listed as follows:


The following table lists General known issues.

Table 16 General Known Issues

Problem ID 



(Windows 2003 only) Report generation fails with lganalyz.exe application error in Sun Java System Web Server 6.1 SP6.


  1. Log in to the web server machine.

  2. Go to WSinstall\bin\https\httpadmin\bin.

  3. Run the flexanlg util command to get the report, for example, C:/Sun/WEBSER~1.1/extras/flexanlg/flexanlg -F -n jwsoffice -x -i C:/Sun/WEBSER~1.1/HTTPS-~2/logs/access -c hnrfeuok -t s5m5h10 -l c+5h5 -p ctl

Note –
  • Type the above command in a continuous line.

  • Replace jwsoffice with your hostname or IP address. You also can export the output to an HTML file and use a browser to view it. For more information on the flexanlg utility, see Sun Java System Web Server 6.1 SP10 Administrator's Guide.


Sun Java System Web Server 6.1 SP8, when run with JDK 6 shows the search collection names (checkbox) in a different order in the search pages, as compared to when it is run with older JDK versions. 


JES3: Patch upgrade of web server on Linux displays false uninstall notification. 



Contents do not get updated under a particular situation on HP-UX 11.0 platforms. 

The HP-UX operating system has two cache spaces, 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 a text editor to update the contents each time.


Searching of Users and Groups through LDAP server using Administration Graphical User Interface fails. 

Workaround: For this feature to work, install Red Hat AS 3.0 update 1–uname -r: 2.4.21-9.ELsmp.


Authorization dialog appears for an unprotected directory without an index file. 

Additional information: If a directory does not have an index file such as index.html, index.jsp, or home.html, then while turning on ACL authentication anyone with read and write permission is denied the list access even though this directory is unprotected.

Workaround: To revert back to the previous behavior of 6.1, change the default ACL so that anonymous users are allowed list privileges. Make the change as follows:

allow (read, execute, info, list) user = "anyone"


Web server fails to startup with JDK 1.5 initialization. 


Set the following in the start script: 



The following table lists the known issues in Administration.

Table 17 Known Issues in Administration

Problem ID 




If you remove a listen socket or change its port number and restart or reconfigure the server, the server fails to close the old listen socket. The operating system continues to accept connections on that port, but the server will not respond to requests on that port. 

Work around: Close the old listen socket, stop the server and restart it.


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


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 the escape character. Use `\' on the 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


Unable to manage Directory Server user/group/ou using Sun Java System Web Server 6.1 SP2 Administration on RedHat Linux Advance Server 3.0.


View Access and View Error does not work properly with multibyte characters. 


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.

The newly created LDAP Administration user must have the same password as the web server Administration user. 


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.


Sun Java System Web Server 6.0 SP4: Cannot enable Distributed Administration when using SASL and anonymous bind. 

Workaround: Do not use anonymous bind to an SSL-enabled directory server.


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.


The End User Administration feature (under Distributed Administration in the Administration interface) is no longer supported. 


Inconsistent look and feel of the Administration GUI. 


The Add Server page in the Administration GUI disappears in Netscape Navigator 7.0 when insufficient information is provided. 

Workaround: Provide 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 Navigator 7.0.


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. 


Superusers 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.


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.


.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


Web server is 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.


JSP applications are not accessible from Sun Java System Web Server 6.1 when the 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"


Service fn="service-passthrough" servers="http://server:port"


No Administration GUI feature is available to delete JSP ClassCache files.


The Administration GUI says Click Apply for the changes to take affect but no Apply button exists in the Administration Server. 


The SNMP web server subagent doesn't answer to snmpwalk command on Solaris 10. 

The SNMP master agent bundled with Sun Java System Web Server 6.1 hangs on Solaris 10 U2 (and higher) due to the TCP fusion feature added in Solaris 10 U2. 

Workaround: Use either of these two workaround:

  • Disable TCP fusion by adding the following line in /etc/system:

    set ip:do_tcp_fusion = 0x0

  • Change the tcp_xmit_hiwat value to a higher value like 262144.

    # ndd -set /dev/tcp tcp_xmit_hiwat 262144

    Peer snmp master agent functions properly.

    If you are setting tcp_xmit_hiwat value, you may put it into rc script to avoid setting it manually after system reboot.


ACL did not update USERDB in server.xml , then [NSACL6000] HTTP5239 errors when access page 

When you use a non-default authdb for ACL, ensure that the authdb detail has been added to server.xml. Else, the server will throw an error later when you access the page protected by ACL as :

[NSACL6000] HTTP5239: digestrealm is not a registered database


The error is because, the server.xml still has USERDB as “default” and cannot find the “digest1” for ACL as shown below:.

<VSCLASS id="vsclass1" objectfile="obj.conf">
  <VS id="https-testdigest" connections="lsl" mime="mime1"
  aclids="acll" urlhosts="apple">
			<PROPERTY name="docroot" value="/export/home/iws6.1sp9/docs"/>
			<USERDB id="default"/>

Add manually the below information into server.xml, after default USERDB declaration under the required virtual server, and restart the server.

<USERDB id="digestrealm" database="digestrealm"/>

You also need to ensure that authdb has been rightly mentioned in the dbswitch.conf and ACL file.

In dbswitch.conf file:

apple:/export/home/iws6.1sp9> cat userdb/dbswitch.conf 
directory digestrealm file 
digestrealm:syntax digest 
digestrealm:digestfile /export/home/iws6.1sp9/digestrealm

In ACL file: 

acl "default";
authenticate (user,group) {
        database = "digestrealm";
        method = "digest";
        prompt = "digestrealm";
deny (all)
 (user = "anyone");

allow (read,execute,list,info)
 (user = "all");


The following table lists the known issues in Core.

Table 18 Known Issues in Core

Problem ID 



webservd child process orphaned when Solaris crypto softtoken ( is used in Sun Java System 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.


Web server crashing configured with an NFS-mounted docroot directory 

Web server crashes if NFS file is removed or replaced, while using NFS and MediumFileSizeLimit >0. Therefore, you should not use MediumFileSizeLimit>0, if the document root is mounted over NFS.


When Web server documents are residing on an NFS mount, as in NFS client, set MediumFileSizeLimit to 0 in nsfc.conf.

Documentation and Online Help

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

Note –

For a list of known issues in the localized versions of 6.1 documentation, see Issues Resolved in 6.1 Documentation.

Table 19 Known Issues in Documentation

Problem ID 



Online Help indicates that the maximum characters for an authentication password is eight characters. 

Additional Information: The authentication characters for an authentication password can be more that eight characters.


No documentation available regarding feature upgrades.  

Additional Information: See Installation, Upgrade, and Migration Notes.


Need to doc the non-existance of <instance>/lib 

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.


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

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


The following table lists the known issues in Installation.

Table 20 Known Issues in Installation

Problem ID 



AIX Web server fails to start with JDK 1.5. 


Set the following in the start script. 



JDK only upgrade results in disabling search. The user receives an exception, and the search page is not accessible from the GUI. 

Workaround: This exception does not happen if Sun Java System Web Server 6.1 SP2 core is installed along with or prior to installing JDK alone. In addition, if Sun Java System Web Server 6.1 SP2 core is installed on top of a JDK-upgraded Sun Java System Web Server 6.1 SP1, the exception does not show up.


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 not install the web server into a directory with spaces in the name.


On the Windows platform, the Sun Java System Web Server installer does not accept 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 field allows you to type up to 256 characters.


On the Solaris platform, Control-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.


On the AIX platform, Control-C makes the terminal screen hang during installation. 

This problem occurs on the screen used to specify the name of the computer on which the web server will be installed. 


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:




The following table lists the known issues in Migration.

Table 21 Known Issues in Migration

Problem ID 



Cannot enable Java on a migrated 4.1 instance even after opting to enable JAVA at the time of migration and enabling from the GUI after migration. 

Workaround: Manually add the following entries to the obj.conf file and restart the instance:

<Object name="default">
	NameTrans fn="ntrans-j2ee" name="j2ee"
	NameTrans ......
	PathCheck .....
	ObjectType ......
	Service .......
	Error fn="error-j2ee"
	AddLog .....

<Object .....

<Object name="j2ee">
	Service fn="service-j2ee" method="*"


Cannot change the document root of a migrated server from 4.1. 

Workaround: Edit the migrated instance's obj.conf and server.xml manually. These files are located under SERVER_ROOT/HTTPS-INSTANCE/config directory.

In obj.conf change the line

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


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

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

<PROPERTY name="docroot" value="existing-doc-root">


<PROPERTY name="docroot" value="new-doc-root">


ktsearch.jar is not 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


Web application file status ignored during migration from 6.0 to 6.1 

Web application status defined at the file level in the server.xml file is not migrated. If a user has switched off the status of the web applications file to suppress them, upon migration these web applications are exposed.

Workaround: Edit the server.xml file of the migrated instance and turn off status for each web application.


Installation of SP_2 patch on existing install (update) 

If you want 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, 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 22 Known Issues in Samples

Problem ID 



Simple JSP files throw an exception due to the distributable tag in web.xml.


  1. Remove the tag distributable from the web.xml file in the /simple/src directory.

  2. Redeploy the web application.

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 build tool and must be downloaded from Apache at 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: 

<PROPERTY name="dbdrivername" value="oracle.jdbc.pool.OracleDataSource">


<PROPERTY name="dbdrivername" value="oracle.jdbc.driver.OracleDriver">


The following table lists the known issues in Search.

Table 23 Known Issues in Search

Problem ID 




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

Workaround: To change the default order, add `+' as a first character of the sort string. Because `+' 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.


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

Workaround: Rebuild the entire collection by performing one of the following actions:

  • Remove all documents and add them back again.

  • Delete the collection and create it again.


Search does not work when you search for a word using a different case pattern. 

Search results are not displayed on the the search page if you search using a word of mixed case. For example, typing sAmpLe instead of sample or SAMPLE. 


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

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

PHSS_28871 — ld/linker cumulative patch


Search engine fails to index password protected PDF document 

If a PDF document is password protected and encrypted, the search engine fails to index the document's metadata. As a result, the requested search fails. 


Sun Java System Web Server 6.1 SP10 64-bit solaris sparc, few search tests fails when JDK 1.6.0_07 used. 

While running search tests, a few test cases fail with stack overflow error when JDK 1.6.0_07 is used. Whereas, the same test passes with bundled JDK 1.5.0_16.  

Workaround: Increase the StackSize value from 131072 to a value, for example, 262144 in the magnus.conf file.


The following table lists the known issues in Security.

Table 24 Known Issues in Security

Problem ID 



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. 


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.


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 you can obtain a directory listing even if the applicable ACLs deny the list right.

If you need to restrict directory indexing, disable 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.



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 problem only occurs when web server is installed as part of the JES3/JES4 install. The problem does not exist in stand-alone (file-based) installation.  


  1. Copy the library from the file-based installation of web server and paste it to the following location in your current setup: /opt/SUNWwbsvr/bin/https/lib

  2. Restart the web server.


The following table lists the known issues in Tools.

Table 25 Known Issues in Tools

Problem ID 



On Windows, deployment fails if the class file depth along with the file name exceeds 255 characters. 


On Linux, a null pointer exception is thrown when deploying an application using the wdeploy command-line utility. This problem 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. Check whether the server did 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 26 Known Issues in the Web Container

Problem ID 



Java logging issues in a deployed module. 


Issue on Windows related to the case of url-patterns.

As per the Servlet specification, the url-pattern elements in web.xml are case sensitive. This condition might lead to unexpected behavior for Windows users, for example, if a client makes a request for index.HTML expecting this string to match index.html.


The following table lists the known issues in WebDAV.

Table 27 Known Issues in WebDAV

Problem ID 



Unable to rename or move a resource if the parent directory is locked exclusively. 

This problem 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.


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 28 Known Issues in the Localization

Problem ID 



The Administration online help of web server is not localized.  

The Administration online help has been localized only up to the first level. The initial help pages are localized but clicking the links on a page, for example, Removing a Server displays help content in the English language. 


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 the English language.

Workaround: Set the browser's prefer locale to zh to view the online help in the Chinese language.


Sun Java System Web server 6.1 SP8: In Internet Explorer 7, you can select the locale as ja or ja-JP. If you select the locale as ja, online help is displayed in Japanese. But when you select the locale as ja-JP, online help is displayed in the English language.