This section lists the important known issues and limitations at the time of Web Server 7.0 beta release.
The following table lists the known issues in installation.
Table 1–3 Known Issues in Installation
Problem ID |
Description |
---|---|
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. |
The following table lists the known issues in migration.
Table 1–4 Known Issues in Migration
For detailed migration information, see the Sun Java System Web Server 7.0 Installation and Migration Guide. This guide contains information about migrating from version 4.1 to 7.0, and from version 6 and compatible versions to 7.0.
The following table lists the known issues in the core of the server.
Table 1–5 Known Issues in Core
Problem ID |
Description |
---|---|
6395374 |
Incorrect hostname for Web Server on Windows |
The following table lists the known issues in the administration.
Table 1–6 Known Issues in Administration
Problem ID |
Description |
|||
---|---|---|---|---|
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:
Workaround: Follow these steps:
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: Note – 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:
|
|||
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.
|
|||
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. |
The following table lists the known issues in the localized version of Web Server 7.0.
Table 1–7 Localization Issues
Problem ID |
Description |
---|---|
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.
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.
|
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
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.
|
6385933 |
After creating the configuration, a multi-byte name becomes garbage.
|
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.
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:
|
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.
|
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. |