test

Sun Java System Web Server 7.0 Release Notes for Microsoft Windows

Administration

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: 


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:

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: 

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