Sun Java System Web Server 7.0 Update 1 Release Notes

Known Issues

This section lists the important known issues and limitations at the time of Web Server 7.0 Update 1 release.


The following table lists the known issues in the administration of Web Server.

Table 4 Known Issues in Administration

Problem ID 



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

It is possible to register a node to a second Administration Server without canceling the registration with the first Administration Server. However, this leads to the nodes becoming inaccessible to both the Administration Servers. 


On each registration, restart the administration node. The administration node will be available to the most recent Administration Server it has registered to. 


wadm command allows connecting to a node, shows a certificate and then throws a 'HTTP 400 Error'.

When an administration node receives a connection, the administration node does not check the connection is from the Administration Server before proceeding. It not only prints an inappropriate error message, but also prompts the user to enter the password.  


Cannot access shell/system variables from wadm.


wadm does not inherit the shell environment variables. However, to make the shell variables it available to wadm, use

"java::call System getenv env_var_name

For example: 

For accessing the shell environment variable MAIL from within wadm, type the following command at the wadm prompt:

wadm> java::call System getenv "MAIL"


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 enter a user name and password. This occurs because the default Access Control List (ACL) in Web Server 7.0 grants the list access right only to authenticated users. 


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


Session replication enabled instances does not come up normally, if other instances in the cluster are not started.


After migrating the Java keystore keycerts using the migrate-jks-keycert command, trying to list the migrated jks keycerts using the list-certs command, displays the CN, org and other information instead of the certificate nickname.


While setting the SSL property using the wadm set-ssl-prop command, the server-cert-nickname property accepts any certificate nickname, instead of accepting only the server certificate nickname.


The set-session-replication-prop CLI command does not work if the 'node' option is provided with a qualified domain name.


Use the output of the list-nodes command for the valid names of the nodes in the set-session-replication-prop command.


Setting digestauthstate property through the set-authdb-prop CLI does not validate the value and allows to set junk value for this property.


Specifying "yes" at the wadm prompt crashes the CLI.


When you try to connect to the Administration Server after the administration certificates have expired, an incorrect error message is displayed.


The register-node command gives an incorrect error message when the Administration server runs out of disk space.


If no disk space is available on the device, wadm throws an incorrect error message "Unable to communicate with the administration server".


Executing the migrate-server command with both "--all" and "--instance" options does not result in an error.

A warning or an error message should be displayed indicating that the user is attempting the set mutually exclusive options. 


The Start Instances. button in the Admin Console is enabled for instance which is already running.

The buttons should be enabled or disabled based on the status of the instance. 


wadm allows you to define duplicate user properties.

Adding duplicate user properties does not show an error message; however, a new user property is not created. 


There is no provision to create new Access Control List (ACL) file using the Admin Console or the CLI.


On Windows, using an existing configuration, repeating the process of adding and removing the registered nodes causes validation failure.


Clicking on the Version button in the Admin Console result in “file not found” warning in Administration error logs.


MIME Types allows MIME value with multibyte characters.


Text in Access Control List page is not formatted.


User can be switched between `available' and `selected' lists in ACE even though the user is deleted from the authentication database.


No warning is issued before the deletion of key or the digestfile authentication database.


When a single user in group is deleted, an incorrect message “Group Saved Successfully" is displayed.


Administration Interface allows you to create a new user with multi-byte User ID in the keyfile authentication database.


User and Group table in the Admin Console displays the entire result in a single page.


Labeling of the Request Certificate and Install buttons in the Admin Console Create Self-Signed Certificate page needs to be revised.


Add and Remove buttons are enabled in new ACE window even if no items are present in the `Available' list.


Admin Console truncates the display of server logs at 50 lines or 2 pages.


No validation exist to check the entry of wrong country code in the certificate request wizard.


In the Admin Console, no text field description is provided for virtual-server, authdb, dav collection, and event fields .


Admin Console shows wrong JDK version while creating a new configuration.

The JDK version displayed in the Admin Console is 5.0 u6 instead of 5.0 u7. 


Style formatting is lost after restarting the Administration Server from Nodes -> Administration Server General tab.


Attempting to access the Admin Console in another tab of the same browser does not work.


View Log displays result in a single page.

Although the search criteria selected for record size is 25 log entries, the log displays the results in one single page even if there are more than 50 log entries. 


Token mismatch error is displayed when you remove the token password and then reset it in the Common tasks -> Select configuration -> Edit configuration -> Certificates -> PKCS11 Tokens page.


The Virtual Server Management->Content Handling->Document Directories->Add should have a browse option to choose the path of a additional document directory.


Message displayed about WebDAV collection locks in the Admin Console is misleading.

If you specify the time-out value for the WebDAV collection as infinite, the Common Tasks->Select Configuration ->Select Virtual Server->Edit Virtual Sever ->WebDAV->Select collection page displays the message DOES NOT EXPIRE. What it actually means is that the lock does not expire automatically after a specified time or the time-out is infinite.


Incorrect error message is displayed on setting empty token password using the `Set passwords' button.


Admin Console displayed incorrect failure messages on certificate creation and deletion.


Instance fails to restart if you try to edit a token password and deploy a configuration on an instance which is already running.


The Admin Console displays an exception when you delete a configuration and click on the Migrate button.


The Admin Console Review screen in wizards should only show fields that have values.


During migration, the log-dir path permission is not validated.


The Results page in all Admin Console wizards should be aligned properly.


Cannot log in through the Administration CLI if the administration password has extended ASCII characters.


The error-response file name should be validated.


Inconsistent behavior while starting an unregistered administration node.


Administration server starts with expired certificate; wadm should warn about expired certificates.


The create-instance command fails on remote node intermittently and logs HTTP 400 error.


The unregister-node command should also clean up certificates on the administration node.


WebDAV lock CLIs do not work in a cluster environment.


Multiple installations of the administration nodes on the same node that is registered to the same administration server should be not be allowed.


Accessing the administration node URL results in Page Not Found error.

As the administration node does not have a GUI, accessing the administration node URL results in Page Not Found error.


The default server.xml should not contain the <stack-size> element.


No validation for class path prefix and suffix, and native library path in JVM Path Settings in Java.


The server.xml elements should be grouped based on functionality.


Exception in administration error logs on creating new configuration with instance.


Web Server should store its pid file and UNIX domain sockets in /var/run instead of /tmp.


On Windows. Administration server moves the Web application files physically before stopping the Web application.


Executing the create-instance command immediately after starting a remote node fails on the remote node.


View server logs page throws error if the access log format is not in Common Log Format (CLF).


The Admin Console misleads user with "Instance modified" message when runtime files gets created in the config directory.


Trust store does not deleted on uninstalling the administration node after unregistering it with the administration server.


The list-cert command does not list the certificates if the certificate nickname contains a colon.


Changes made to the JavaHome property does not get saved after restarting the instance.


<pkcs11> element not removed from server.xml even when child elements are absent.


<pkcs11/> added to server.xml when token pin is set.


No obvious way to reset the administration server password.


  1. Comment out the security-constraint in install_dir/lib/webapps/jmxconnectorapp/WEB-INF/web.xml.

  2. Restart the Administration Server.

    This action turns off the authentication on the administration server.

  3. Set the administration password by using the set-admin-prop command.


[JESMF CONFORM] CP when stopping should call MfManagedElementServer_stop().


Need better validation in certain text fields to prevent obj.conf file corruption.

Most of the functional validation of the data in a form is done in the back end. The GUI has only minimal checks such as empty fields, integer values, and ASCII values. Hence, the GUI stores the data in the obj.conf when parsed gets corrupted .


Admin Server does not time-out if the server instance restart does not respond.

On UNIX systems, the Administration Server waits until the server instance is restarted when the restart-instance command is executed. If the instance is not successfully restarted, the Administration Server does not respond to requests.


Executing the restart-admin command followed by the stop-admin command throws exception in administration error logs.


SNMP master agent process fails to start on Web Server


Changing the tcp_xmit_hiwat value to a higher value like 262144 , peer SNMP master agent functions properly. Type the following command to change the tcp_xmit_hiwat value.

# ndd -set /dev/tcp tcp_xmit_hiwat 262144


Cannot edit WebDAV collection properties through the Admin Console

When a configuration is deployed on multiple nodes, the lockdb path must be a shared location mounted on the same path on all the nodes. Additionally, to list or expire locks in the lockdb from the Admin Console, the same path must be writable from the Administration Server.


On Windows, wdeploy command fails if older version of libnspr4.dll is found in the system32 directory.


Before calling Java, edit the wdeploy.bat file that is available in install_dir/bin directory. Change the path of the Java directory to install_dir/lib directory. This modification makes Windows look for libnspr4.dll in the install_dir/lib directory before it looks in system32 directory.


The add-webapp command when used with JSP pre-compilation option does not delete the previously precompiled JSP files.


The Admin Console or the Admin CLI does not provide support to add CA certificates to the Administration Server.


On Windows, the Admin Console intermittently fails to come up.


  1. This problem is seen on Windows 2003 if you have "Internet Explorer Enhanced Security Configuration" enabled.

  2. To access the Admin Console without disabling Enhanced Security feature, include the site in the list of trusted sites explicitly on the browser.

  3. Go to Control Panel > Add/Remove Programs > Add/Remove Windows Components.

  4. Deselect the check box next to Internet Explorer Enhanced Security Configuration.


The following table lists the known issues in the core of Web Server.

Table 5 Known Issues in Core

Problem ID 



When there is an error executing an obj.conf directive, the filename and line number where the offending directive was found are not logged.


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.


All HTTP header parsing error are not logged with the client IP and a description of the error.


set-variable SAF could not set predefined variable.


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.


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.


'external' expression function with quoted path is not working.


On HP-UX, SNMP fails for some oid values.


Due to lack of the HP-UX API support and complexity, network in and out traffic statistics is not implemented. Use HP tools for monitoring the traffic statistics. 


On HP-UX 11.11, Web Server fails to start when max heap size is 2048 MBytes or greater.


  1. Ensure that patch PHKL_28428 or its updated version is present on the system. If it is not present, install the patch.

  2. Type the following commands before starting the Web Server:

    • For 1500 MBytes to 2400 MBytes of Java heap: Type the following command before starting the Web Server:

      chatr +q3p enable /opt/sun/webserver7/lib/webservd

    • For 2400 MBytes to 3.8 GBytes of Java heap: type the following command before starting the Web Server:

      chatr +q3p enable +q4p enable /opt/sun/webserver7/lib/webservd

  3. Start the server.

    /opt/sun/webserver7/lib is the default location of the webservd binary.

Documentation and Online Help

The following table lists the known issues in Web Server 7.0 documentation and online help.

Table 6 Known Issues in Documentation and Online Help

Problem ID 



The basic-search.html has unclear description.


The following table lists the known issues in the FastCGI.

Table 7 Known Issues in FastCGI

Problem ID 



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 8 Known Issues in Installation

Problem ID 



Installing the stand-alone product over an existing Java ES installation and vice-versa is not supported.

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


Web Server cannot be installed without installing compat-libstdc++.


On newer versions of Linux, for example, Red Hat Enterprise Linux 3, install compat-libstdc++ before installing Web Server 7.0.


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. 


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.


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. 


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. 


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. 


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.

Migration and Upgrade

The following table lists the known issues in the migration and upgrade areas of Web Server.

Table 9 Known Issues in Migration and Upgrade

Problem ID 



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.


6.x -> 7.0: Migrated scheduled events still points to 6.x paths in the server.xml file.



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.


6.x->7.0: Migration ignores any "document-root" NameTrans specified in the obj.conf file.


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. 


Web Server 7.0 migration tool is unable to successfully migrate from Web Server 6.1 if it has Root Certs installed in it.


Unclear error message if CLI and Administration Server versions are incompatible.

While upgrading Web Server 7.0 installation to Web Server 7.0 Update 1 , make sure that the entire setup CLI, Administration Server and all the Administration Nodes are also upgraded to Web Server 7.0 Update 1. This is because, Web Server 7.0 administration interfaces will not work correctly with Web Server 7.0 Update 1 administration interfaces. 

Sample Applications

The following table lists the known issues in Sample Applications of Web Server.

Table 10 Known Issues in Sample Applications

Problem ID 



sendmail.jsp shows incorrect file to be edited to specify for javamail sample application.


To set, edit the and not the build.xml as specified in install_dir/samples/java/webapps/javamail/src/docroot/sendmail.jsp.


Sample applications documentation must mention adding jar file to the class path in the properties file.

In the install-dir/samples/java/webapps/security/jdbcrealm/docs/index.html, under 'Compiling and Assembling the Application' section, there must be a mention of adding JDBC driver jar file to class path suffix in the file.


The following table lists the known issues in the search functionality of Web Server 7.0.

Table 11 Known Issues in Search

Problem ID 



server.xml does not store the full file pattern for converting and including search .

The schema does not store the full file pattern allowed by both the Admin Console and the search administration tools in this version of the Web Server. It also has no way to represent the full file pattern that might sometimes need migration from the previous versions of the Web Server.  


The following table lists the known issues in the security area of Web Server.

Table 12 Known Issues in Security

Problem ID 



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. 


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.


Request to the server fails with using of "Sun Software PKCS#11 softtoken".

Refer to the following documents for additional info on configuring the Web Server with Solaris 10 libpkcs11:

Session Replication

The following table lists the known issues in the session replication functionality of Web Server 7.0.

Table 13 Known Issues in Session Replication

Problem ID 



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. 


Session replication does not failover correctly when cookies are disabled on the client.


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.

Web Container

The following table lists the known issues in the web container of Web Server.

Table 14 Known Issues in Web Container

Problem ID 



Web container writes to stderr.


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.



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.


No information is logged in error logs at the finest log level on successful JNDI resource creation.

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


Servlet container collects statistics when stats enabled element is set to false in the server.xml file.


Servlet container creates a thread per virtual server.


Values of 'mail-resource' sub elements are not getting set on mail session object.


NSAPIRequest.setupRequestFields is slow.

com.sun.webserver.connector.nsapi.NSAPIRequest.setupRequestFields is slow primarily because of excessive String-->byte and byte-->String conversion when parsing Cookie headers.


Java garbage collector activity is higher in Web Server 7.0 when compared against Web Server 6.1.

The servlet container in Web Server 7.0 creates many Java objects. 


If a servlet is mapped to req URI formed by partial req + welcome file, the behavior is wrong.

If a web container receives a valid partial request, the web container must examine the welcome file list defined in the deployment descriptor. The welcome file list is an ordered list of partial URLs with no trailing or leading /. The Web Server must append each welcome file in the order specified in the deployment descriptor to the partial request and check whether a static resource or a servlet in the WAR file is mapped to that request URI. The web container must send the request to the first resource in the WAR that matches.


REQ_EXIT causes javax.servlet.ServletException.


JSF Web Applications running on Web Server 7.0 may break when running on Web Server 7.0 Update 1.

Web Server 7.0 Update 1 ships with JavaServer Faces 1.2 technology. All JavaServer Faces web applications are expected to work with Web Server 7.0 Update 1 without any modifications. However, there are a few known compatibility issues with JavaServer Faces 1.2 and might require applications to be modified to address these incompatibilities. The incompatibilities are documented in the JavaServer Faces release notes at:

Java ES 5 Portal Server users are suggested to delay upgrading to Web Server 7.0 Update 1 until Java ES 5 Update 1 is released.  


The following table lists the known issues in the localized version of Web Server.

Table 15 Known Issues in Localization

Problem ID 



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

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


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: 

<parameter-encoding form-hint-field="j_encoding"/>
<property name="use-responseCT-for-headers" value="true" />


On Windows and HP-UX, 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.  


Search filter “*” does not work correctly for multi-byte strings.


On Windows 2003, when a command is executed from the CLI, the message is not encoded correctly.


The hardcoded message "ADMIN3594: Configuration changes require a server restart" is not localized.


In the Japanese locale online help, the description about the PAM for "Editing Authentication Databases" incorrectly states the name of Directory Server.  

The description must be read as: "Editing Authentication Databases" PAM -- PAM is the new auth-db supported by Sun Java System Web Server 7.0.  


Search collection subdirectory with leading slash causes confusing error. 

When you try to create a search collection and set the document root subdirectory with a leading slash, the error message produced wrongly informs you that a slash at the beginning is needed. 


Inconsistent wording found in Directory listing type. 

The sentence "Error response file to use when indexing is None" should be changed to "Error response file to use when listing is None". 


The word "Other" in the list of countries is not translated. 


In the Add Documents window, Included checkbox for subdirectory is not translated.  

Java Enterprise System

The following table lists the known issues in the Java Enterprise System (Java ES).

Table 16 Known Issues in Java ES

Problem ID 



Portal Server configures JVM stack size to 128K (too low) for Web Server 7.0 64–bit to start.

If Web Server 7.0 is already configured in 64–bit mode, and the Portal Server installation is started, Portal Server configuration does not set stack size to 128K. However, if both Portal Server and Web Server are already installed and configured in 32–bit mode, switching to 64–bit mode involve series of manual steps that are described in the Workaround section. 


If Portal Server part of Java ES 5 is deployed on top of the 32–bit version of Web Server 7.0, and if you would like to start the server in 64-bit mode, perform the following steps: 

  1. # install_dir/bin/wadm delete-jvm-options --user=admin --port=8989 --password-file=passfile --config=HOST_NAME "-Xms512M -Xmx768M -Xss128k"

  2. # install_dir/bin/wadm create-jvm-options --user=admin --port=8989 --password-file=passfile --config=HOST_NAME "-Xms512M -Xmx768M -Xss512k"

  3. Increase the native stack size of Web Server 7.0 to 139264 by typing the following command:

    # install_dir/bin/wadm set-thread-pool --user=admin --config=config_name --password-file=filename native-stack-size=139264

  4. Deploy the configuration.

    # install_dir/bin/wadm deploy-config


schemagen/xjc/wsgen/wsimport scripts not present in Java ES Web Server installation.

schemagen/xjc/wsgen/wsimport scripts are present in different locations in Java ES installation and stand-alone installation of Web Server.


The scripts are part of the Web Services components. In a stand-alone Web Server installation, these scripts and JAR files are located in install_dir/bin and install_dir/lib directories respectively.

In Java ES installation, scripts and JAR files are installed as part of the shared component and they reside outside the Web Server installation root.  

The location of scripts and JAR files on different platforms are listed below: 

Solaris OS: 

  • Scripts are under /opt/SUNWjax/bin directory.

  • JAR files are under /opt/SUNWjax/lib and /usr/share/lib directory.

Linux and HP-UX: 

  • scripts are under /opt/sun/bin and /opt/sun/share/jaxb/bin directories.

  • JAR files are under /opt/sun/share/jaxb/lib, /opt/sun/share/lib and /opt/sun/private/share/lib directories.


  • Scripts are under <JES_installation_dir>\share\bin and <JES_installation_dir>\share\jaxb2\bin directories.

  • JAR files are under <JES_installation_dir>\share\jaxb2\lib and <JES_installation_dir>\share\lib directories.


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.  


Note –

Move the existing and 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 < path>:< path> in the following commands.

On Solaris platform, perform the following steps: 

  1. Copy the and files from Web Server 6.1 lib directory to an appropriate location.

    Note –

    For HP-UX, the files are and For windows, the files are libdb-3.3.dll and libdb_java-3.3.dll.

    Caution – Caution –

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

  2. Create a directory (mkdir) by name /portal_libraries. Copy the library files and to /portal_libraries.

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

  4. Get the current native library path setting by typing the following administration CLI command:

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

    Save the output.

  5. Append the copied and path to the existing native library path by typing the following administration CLI command.

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

    where, portal-libraries-path is the location of where you copied the and files in Step 1.

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


  6. Note –

    For Windows platform, use ';' as the separator for 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>

  7. Deploy the modified configuration by typing the following command:

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


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.


A lot of warnings/info messages displayed at Web Server startup on the standard output instead of routing these messages to the log file.


Web Server running on Windows contains no description for the service and the description is not updated after applying Java ES Update 1 patches.


When upgrading Java ES 5 software to Java ES 5 Update 1, Portal Server samples fail with JSF exceptions if you have upgraded only Web Server but not the Portal Server.

For more information, see Compatibility Issues.