This section lists the important known issues and limitations at the time of Web Server 7.0 Update 4 release.
The following table lists the known issues in the administration of Web Server.
Table 4 Known Issues in Administration
The following table lists the known issues in the core of Web Server.
Table 5 Known Issues in Core
Problem ID |
Description |
---|---|
6785490 |
Any URI that does not end with the "real" file name fails to execute properly, resulting in a “No input file specified” error. For PHP users: Web Server 7.0 Update 4 populates the environment variables REQUEST_URI and SCRIPT_FILENAME for FastCGI and CGI applications. The introduction of the SCRIPT_FILENAME variable causes PHP to display a No input file specified PHP error for scripts that are mapped to virtual URIs, that is, URLs ending with / instead of /index.html or URLs making use of Web Server 7.0's URI rewriting feature. The affected PHP versions are 5.2.5 through 5.2.8. For more information, see http://bugs.php.net/bug.php?id=47042. Workaround: If a PHP application is mapped to a virtual URI, then cgi.fix_pathinfo should be set to 0 in the php.ini file. This setting is required for many popular PHP applications like Drupal, Wordpress, Joomla, etc. However, this setting will cause PHP applications that rely on path-info like /foobar.php/baz/ to return a No input file specified PHP error. If a PHP application relies on path-info, then cgi.fix_pathinfo should not be disabled. |
6296993 |
When there is an error executing an obj.conf directive, the filename and line number where the offending directive was found are not logged. |
6365160 |
When server.xml schema validation fails due to a data type constraint violation, it displays an error message that does not describe the set of valid values for the element. |
6378940 |
All HTTP header parsing error are not logged with the client IP and a description of the error. |
6470552 |
set-variable SAF could not set predefined variable. |
6486480 |
service-nsfc-dump entry hit counts are 0 with <replacement>false</replacement>. If <replacement>false</replacement> is specified in server.xml file, entry hit counts show as 0 in the service-nsfc-dump output. However, the cache hit counts are displayed correctly. |
6489220 |
Server treats non-interpolated strings that contain $$ character constants as interpolated. When a parameter value contains a $$ escape, the server constructs a PblockModel for the parameter block. This is unnecessary because $$ is a constant. |
6641109 |
Webserver 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. Workaround: When Web Server documents are residing on an NFS mount, as in NFS client, set MediumFileSizeLimit to 0 in nsfc.conf. |
6775948 |
Include file missing in nsapi.h throws a warning message while compiling some NSAPI modules. Workaround: Add include <netdb.h> before nsapi.h. |
The following table lists the known issues in the FastCGI.
Table 6 Known Issues in FastCGI
Problem ID |
Description |
---|---|
6485248 |
The fastcgi stub does not properly close all the processes when reuse-connection is set to true. Configure Web Server 7.0 to work with PHP as a FastCGI plug-in and set reuse-connection=true. When you shutting down the server or reconfiguring the server, the fastcgi() process and its child processes are left behind and not killed properly. |
The following table lists the known issues in the installation of Web Server.
Table 7 Known Issues in Installation
Problem ID |
Description |
|
---|---|---|
6414539 |
Uninstalling the administration node does not delete itself from the administration server node. After installing the administration node and registering it with the administration server in the Node tab, the administration node is listed in the Node tab. When the administration node is uninstalled, the administration node entry remains in the Node tab. |
|
6287206 |
Cannot install if the setup is started from a shared folder on the network. On the Windows platform, unable to install the product when the installer setup.exe is started from a shared network folder on another machine. |
|
6311607 |
On Windows, installer crashes in CLI mode, if the administration password is >= 8 characters. If the administration user password is greater than eight characters, then 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 on the Windows platform using the command-line interface (CLI), the administration password must be set to less than (<) eight characters. |
|
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 |
The CLI installer does not handle ctrl+c while entering the password. The installer does not accept ctrl+c and hence the terminal becomes unusable. |
|
6710925 |
RH5.1 user cannot install Web Server 7.0 Update 3 using GUI mode Workaround To overcome this failure:
|
|
6717123 |
Registration Options panel UI sometimes doesn't show up properly The 'Registration Options' GUI in the installer does not show up properly sometimes. Workaround: Resizing the installer window will fix this issue. |
The following table lists the known issues in the migration and upgrade areas of Web Server.
Table 8 Known Issues in Migration and Upgrade
Problem ID |
Description |
---|---|
6407877 |
Incorrect migration occurs while migrating from Web Server 6.0 to 7.0 if the installed.pkg file is not found. In Web Server 6.0 to 7.0 migration, if the installed.pkg file is missing, Web Server incorrectly migrates the NSServlet entries in the magnus.conf file. |
6490124 |
6.x -> 7.0: Migrated scheduled events still points to 6.x paths in the server.xml file.
|
6502529 |
6.1->7.0: Migration does not handle relative path set for search-collection-dir correctly. During instance migration, specifying a relative path for the target path into which the search collections should be copied, results in the search collection directory being created with respect to the config-store. When the instance is instantiated, the indexes are created without properly migrating the search collections. |
6502769 |
6.x->7.0: Migration ignores any "document-root" NameTrans specified in the obj.conf file. |
6498806 |
On Windows, Web Server Admin Console does not appropriately warn users during migration. Administration Server does not detect if the selected new configuration or the service name already exists on Windows and hence does not appropriately warn the users to select a different configuration name or suggest a different configuration name as default. |
6500509 |
Web Server 7.0 migration tool is unable to successfully migrate from Web Server 6.1 if it has Root Certs installed in it. |
The following table lists the known issues in Sample Applications of Web Server.
Table 9 Known Issues in Sample Applications
Problem ID |
Description |
---|---|
6472796 |
sendmail.jsp shows incorrect file to be edited to specify resource.host for javamail sample application. Workaround To set javamail.resource.host, edit the javamail.build.properties and not the build.xml as specified in install_dir/samples/java/webapps/javamail/src/docroot/sendmail.jsp. |
The following table lists the know issues in the search functionality of Web Server.
Table 10 Known Issues in Search
Problem ID |
Description |
---|---|
6701532 |
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. |
The following table lists the known issues in the security area of Web Server.
Table 11 Known Issues in Security
Problem ID |
Description |
---|---|
6376901 |
Limitation supporting basic and digest-based ACLs for resources in the same directory. If the server uses digest and basic-based ACLs in different parts of their doc tree, attempting to use both simultaneously on different files or resources in the same directory is not possible. |
6431287 |
TLS_ECDH_RSA_* require the server cert signed with RSA keys. Cipher suites of the form TLS_ECDH_RSA_* requires server to have an ECC keypair with a cert signed using RSA keys. Note that this precludes using these cipher suites with self-signed certificates. This requirement is inherent to these cipher suites and is not a bug. The server should detect and warn about wrong configurations related to these cipher suites but currently it does not do so. |
The following table lists the known issues in the session replication functionality of Web Server 7.0.
Table 12 Known Issues in Session Replication
Problem ID |
Description |
---|---|
6324321 |
Descriptive error message is not displayed when an error occurs remotely. When an exception occurs remotely, error messages are logged in the error log of the remote instance. However, the local instance currently displays a generic remote exception which does not clearly indicate which error log that the user must view. |
6396820 |
Session replication does not failover correctly when cookies are disabled on the client. |
6406176 |
When enabled, session replication should be the default session manager. After enabling session replication by using the Admin Console or the CLI, or by editing the server.xml file, session replication is not really enabled. Instead, sun-web.xml needs to be manually edited. |
The following table lists the known issues in the web container of Web Server.
Table 13 Known Issues in Web Container
Problem ID |
Description |
---|---|
4858178 |
Web container writes to stderr. |
6349517 |
Incorrect web application session statistics for MaxProcs > 1 mode. Web Server runs in multi-process mode. The MaxProcs configuration variable in the magnus.conf is used to set the maximum number of processes. If the value for MaxProcs is set to greater than 1, the Web Server uses mmap-based session manager so that the session could be shared among different JVMs. While collecting statistics from multiple processes, web application MBeans provide session for individual MBeans. There is no way to find the true number of sessions by seeing individual MBean's web application session statistics.
|
6394715 |
Web container deletes the disabled web application MBeans object. When the web application is disabled by setting the <enabled> element to false in the server.xml file, the web container deletes the web application's MBeans and hence treats it as a closed or deleted web application. Since disabled objects are deleted, statistics are also lost. |
6419070 |
No information is logged in error logs at the finest log level on successful JNDI resource creation. |
6422200 |
com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse does 1 byte reads. When reading the server.xml file, the first line containing the XML version number and the encoding is read 1 byte at a time. |
6440064 |
Servlet container creates a thread per virtual server. |
6501184 |
REQ_EXIT causes javax.servlet.ServletException. |
The following table lists the known issues in the localized version of Web Server.
Table 14 Known Issues in Localization
Problem ID |
Description |
||
---|---|---|---|
6543814 |
Search filter “*” does not work correctly for multi-byte strings. |
||
5046634 |
There is no functionality equivalent to use-responseCT-for-headers in Web Server 7.0. Response header encoding is enabled at the web-app level by setting the value of the configuration parameter use-responseCT-for-headers to any of the values; yes, true, or on in the web-app/sun-web.xml file. For example, set Response header encoding as follows:
|
||
6716537 |
Creating socket error message is not localized. |
||
6775946 |
patchrm 125437-15 fails if they are installed in Japanese locale. Installing patchrm 125437-15 in Japanese locale fails and throws the below error:
The log file output is as below:
This issue is observed in the following platforms:
Workaround:
|
The following table lists the known issues in the Java Enterprise System (Java ES).
Table 15 Known Issues in Java ES
Problem ID |
Description |
---|---|
6432106 |
Sun Java System Portal Server search throws exception after Web Server upgrade. Portal Server search functionality throws exception when upgrading Web Server from Java ES 4 to Java ES 5. Workaround Note – Move the existing libdb-3.3.so and libdb_java-3.3.so library files to an appropriate location, somewhere outside the Web Server's private directories. Once the Portal Server libraries are in a suitable location, that path must be specified for the <libdb-3.3.so path>:<libdb_java-3.3.so path> in the following commands. On Solaris platform, perform the following steps:
|
6504178 |
Migration logs reports a bogus "root is not a valid user" message on Java ES 5. While migrating from Java ES 4 to Java ES 5 on UNIX platforms, the migration log file reports WARNING: "root is not a valid user". This is incorrect as the "root" user is valid on that host. |
6453037 |
A lot of warnings/info messages displayed at Web Server startup on the standard output instead of routing these messages to the log file. |