Known Issues

6492159 

Java ES 5 Web Server is creating two instances

Java ES Installer is updating the WS_DOCROOT value in the properties file. For this reason, the configurator is creating two instances for the Web Server. 

Workaround: None.

6408072 

Need icons for objects in Programs folder.

The objects in the Sun Java System Web Server 7.0 folder are created with default Windows program icons and do not have specific icons that denote Sun programs. 

Workaround: None.

6311607 

Installer crashes in CLI mode if the administration password is >= 8 characters.

If the administration user password is greater than eight characters, any invalid input to the administration port, web server port, or the administration user ID crashes the installer. 

Workaround:

When installing Web Server 7.0 by using the command-line interface (CLI), the administration password must be set to less than (<) eight characters. 

6287206 

Cannot install if the setup is started from a shared folder on the network.

On the Windows platform, you are unable to install the product when the installer setup.exe is started from a shared network folder on another machine.

Workaround: None.

6408072 

On Windows, need icons for objects in Programs folder.

The objects in the Sun Java System Web Server 7.0 folder on Windows are created with default Windows program icons and do not have specific icons that denote Sun programs. 

6492144 

On Windows, CLI installer does not handle ctrl+c while entering the password.

The installer does not accept ctrl+c and hence the terminal becomes unusable.

4988156 

Installing the standalone product over an existing JES installation and vice-versa is not supported

Installing the stand-alone product Web Server 7.0 over an existing Java Enterprise System (JES) installation is not supported. JES users of the Web Server must use the JES installer to upgrade to the newer version of the Web Server.  

Workaround: None.

6498416 

Web Server instance creation fails after migration from Java ES 4 to Java ES 5

After migrating Java ES 4 to Java ES 5, if you try to create a Web Server instance for the migrated server, the instance creation fail. The following error message is displayed: 

windows.machine.com:ADMIN3210:Could not create the instance 
because the Windows service "https-jeswin123.india.sun.com' already exists.

For more information , see http://docs.sun.com/app/docs/doc/819-2625/6n4tcivk8.

6493944 

Web Server migration fails on Windows

Workaround: After completing migration, follow these steps to update Root certs library path:

1. List the available root certs.

   "WebServer-base\bin\modutil" -list -nocertdb -dbdir "WebServer-base\admin-server\config-store\test\config"

2. Delete the existing Root certs.

   "WebServer-base\bin\modutil" -dbdir "WebServer-base\admin-server\config-store\test\config" -delete "Root Certs" -force

3. Update the Root certs with correct library path.

   "WebServer-base\bin\modutil" -dbdir "WebServer-base\admin-server\config-store\test\config" -add "Root Certs" -libfile "nssckbi.dll" -force

where WebServer-base is C:\Program Files\Sun\JavaES5\WebServer7 and configuration name is test.

This procedure should be performed after using the migrate command and before using the migrated config command.

6395374 

Incorrect hostname for Web Server on Windows

6513089 

Value missing in the server.xml file when restarting the Web Server instance.

When you restart the Web Server instance, the following error message is displayed: 

a value was missing in the server.xml when restarting the web server instance.

Workaround: Follow these steps:

1. Start the administration server.

   WebServer-base\admin-server\bin\startserv

2. Edit the WebServer-base\https-FQDN\config\server.xml file.

3. Search for the following lines:

   <search-collection> <name/> <..? </search-collection>

4. Replace these lines with the following:

   <search-collection> <name>search-collection-1</name> <..? </search-collection>

5. Bring over these changes to the administration server.

   wadm pull-config --user=admin --config=FQDN FQDN

FQDN is the fully qualified domain name of your host system. 

6492144 

On Windows platform, CLI installer does not process Control+C during password entry.

The installer does not accept Control+C, so the terminal becomes unusable. 

Workaround: None.

6479247 

Dialog box to enter the token password appears on restarting an instance after the deployment. This behavior is not seen on other platforms.

Workaround: None.

6432106 

Sun Java System Portal Server search throws exception after Web Server upgrade.

The Portal Server search functionality throws an exception when upgrading Web Server from Java ES 4 to Java ES 5.  

Workaround:

Move the existing libdb-3.3.dll and libdb_java-3.3.dll library files to an appropriate location, somewhere outside the Web Server's private directories. After the Portal Server libraries are in a suitable location, that path must be specified for the <libdb-3.3.dll path>:<libdb_java-3.3.dll path> in the following commands.

On the Windows platform, perform the following steps: 

1. Copy the libdb-3.3.dll and libdb_java-3.3.dll files from Web Server 6.1 lib directory to an appropriate location.

   ---

   Caution –

   Do not copy the library files to Web Server 7.0 private directories, for example, lib directory.

   ---

2. Create the portal_libraries directory.

3. Copy the library files libdb-3.3.dll and libdb_java-3.3.dll to portal_libraries.

4. Use the wadm command to inform the Web Server about the location of the library files.

5. Obtain the current native library path setting:

   get-jvm-prop -user=admin --config=hostname native-library-path-prefix

6. Save the output.

7. Append the copied libdb-3.3.dll and libdb_java-3.3.dll path to the existing native library path:

   set-jvm-prop --config=hostname native-library-path-prefix=<existing native library-path>:</portal-libraries-path>

   portal-libraries-path is the location of where you copied the libdb-3.3.so and libdb_java-3.3.so files in Step 1.

   If you do not get any results or output for the get-jvm-prop command, set the native-library-path-prefix parameter:

   native-library-path-prefix=</portal-libraries-path>

   ---

   Note –

   Use ';' as the separator for the native-library-path-prefix parameter as follows:

   native-library-path-prefix=<existing native libarary path>;<portal-libraries-path>

   For non-Windows platform, use the ':' as the separator for native-library-path-prefix parameter as follows:

   native-library-path-prefix=<existing native libarary path>:<portal-libraries-path>

   ---

8. Deploy the modified configuration:

   deploy-config [--user=admin-user] config-name

6425144 

wadm does not update classpath correctly if classpath contains semicolon “;”.

When you set the classpath by using the wadm.bat file, if the classpath contains a semicolon, the full classpath is not updated in the server.xml file. Only the path before semicolon “;” is updated.

Workaround: Use one of the following workarounds.

• Use the escape character “\” before the semicolon.

• Use wadm in single mode.

6364924 

A node can be registered to multiple admin servers which may cause a configuration conflict.

You can register a node to a second administration server without canceling the registration with the first administration server. However, this registration leads to the nodes becoming inaccessible to both the administration servers. 

Workaround:

On each registration, restart the Administration Node. The Administration Node is available to the most recent Administration Server to which it has been registered. 

6379125 

wadm allows connecting to node, shows a cert and then throws a HTTP 400 error.

Web Server node uses the same JMX connector as the administration server that is registered at the same URI as an administration server. A certificate is thrown as part of the SSL handshake and the execution has not yet reached the node. Web Server is unable to determine if the connection is from a client or an administration server. 

4793938 

User and password dialog presented instead of directory index.

By default, Web Server 7.0 does not send a directory index unless the user has been authenticated. Attempting to access a directory prompts the user to type a user name and password. This user is prompted because the default Access Control List (ACL) in Web Server 7.0 grants the list access right only to authenticated users. 

Workaround:

You can grant the list access right to unauthenticated users by using the Admin Console or by editing the default.acl file. For more information about how to grant the list access right, see Sun Java System Web Server 7.0 Administrator’s Guide.

6497092 

Windows menus are not localized

The Start-> Sun Microsystems ->Web Server 7.0->Start/Stop Admin Server menus are not localized on Windows. 

Workaround: None.

6483354 

File handle is not released by webservd process under certain conditions.

1. Access the Web Server administration console through the login URL.

2. Select the Configuration tab from the administration page.

3. Select a configuration link, and then select the Virtual Server link.

4. Set Negotiate Client Language to enabled and note your language, such as "zh-CN."

5. Click Save.

6. Restart Web Server by clicking the Deployment pending link in the administration console or manually restart Web Server.

7. In Internet Explorer, type a nonexistent URL, for example, http://yourmachine/xyz.

   The page not found error is displayed in Internet Explorer 6.

Expected Result: The Not found page should be displayed correctly in Internet Explorer instead of the page not found error.

6442101 

Online help Search does not work on non-English locales.

Workaround: None.

6431022 

The files are missing in online help for the link Tips on Searching on all locales.

1. Log in to the admin console as admin.

2. Open the online help window.

3. Click the Search tab in the navigator frame.

4. Click the Tips on Searching link.

   The message Not found appears.

5. Workaround: None.

6419884 

Missing all localization online helps for search.

This issue exists on zh_CN browser. Clicking the help link on the search page displays Not Found error on the browser.

Workaround:

Refer to http:///search/help/zh_CN/basic-search.html instead of http:///search/help/zh/basic-search.html

6412711 

In the localized Administration GUI, part of the Configuration Deployed successfully message is garbled on the Internet Explorer.

Workaround: None.

6385933 

After creating configuration, a multibyte name becomes garbage in Web Server 7

1. Click the Configurations tab.

2. Select Copy or Create Configuration.

3. Type a multi-byte string in the Name of Configuration field and type other information.

   Clicking the Finish button displays the list of configurations that includes a string ??? instead of the typed name. You cannot restart the instance.

Workaround: None.

6492144 

On Windows, CLI installer does not handle Control+C while entering the password.

The installer does not accept Control+C and hence the terminal becomes unusable. 

6494089 

Administration Server node has un-localized string.

• Log in to the Web Server Admin Console as an administrator.

• Click on Nodes tab. Displays un-localized strings, for example, 'This is the Administration Server Node'.

6385933 

After creating the configuration, a multi-byte name becomes garbage.

1. Click on the Configurations tab.

2. Select Copy or Create Configuration.

3. Type a multi-byte string in the Name of Configuration filed and enter other information in the screen.

4. Click the Finish button.

   Displays the list of configurations that includes a string??? instead of the entered name. You cannot restart the instance.

6316881 

Multi-byte characters in headers can not be retrieved by req.getHeader().

The characters are not parsed correctly, when request.getHeader() is called.

5046634 

There is no functionality equivalent to use-responseCT-for-headers in Web Server 7.0.

6503931 

schema.properties file is not localized.

SchemaValidationExceptions caused by the Administration Server result in exception messages being read from the schema.properties file. This file is not localized.

6507819 

On Windows file handle is not released by webservd process under certain conditions.

1. Access the Web Server Admin Console through the login URL.

2. Select the 'Configuration' tab from the administration page.

3. Select a configuration link, and then select the 'Virtual Server' link.

4. Set 'Negotiate Client Language' to enabled and note your language, such as "zh-CN".

5. Click the 'Save' button.

6. Restart Web Server by clicking the 'Deployment pending' link in the Admin Console or manually.

7. In Internet Explorer, type a nonexistent URL, for example, http://yourmachine/xyz. The "page not found" is displayed in Internet Explorer 6.

Expected Result: The "Not found" page should be displayed correctly in Internet Explorer instead of the "page not found" error.  

6507819 

Localized version of Web Server online help contents have some differences from English.

The Japanese online help do not have online help content for the following screens in the Admin Console: 

• Editing Access Log Preferences

• Editing Server Log Preferences

• Archiving Log Files

• Setting Log Rotation

6508299 

Garbage characters are displayed for search results on the left panel of online help of Web Server on non-English locales.

Using Search tab on the online help to search for some content displays garbage characters in the search result page.  

6494089 

Administration Server node has un-localized string.

• Log in to the Web Server Admin Console as an administrator.

• Click on Nodes tab.

  Displays un-localized strings, for example, 'This is the Administration Server Node'.

6502036 

Help window displays an 'Application Error' message in the left pane.

On Linux, accessing Help from the localized version of Admin Console displays an 'Application Error' message.