Sun Java Enterprise System 5 Release Notes for UNIX

This Release Notes document contains important information about Sun Java^TM Enterprise System (Java ES) 5. Read this document before you begin using Java ES in order to improve your overall installation and operation experience. This document is updated as needed to describe new issues as they arise. See Revision History to learn about these updates. The most up-to-date version of this document can be found at the Java ES 5 web site, http://docs.sun.com/coll/1286.2.

Platforms covered: this document covers Java ES for the following platforms:

• Solaris 10 for SPARC^TM, x86, and x64 platforms

• Solaris 9 for SPARC and x86 platforms

• Red Hat Enterprise Linux 4 (AS and ES) for x86 and x64 platforms

• Red Hat Enterprise Linux 3 (AS and ES) for x86 and x64 platforms

• HP-UX 11.11v1 for PA-RISC 2.0 platform

For information about Java ES on the Microsoft Windows platform, see the Sun Java Enterprise System 5 Release Notes for Microsoft Windows.

Components covered: this document covers the Java ES components that are distributed with and installed by the Java ES installer. It does not provide information about Java EScomponents that are distributed and installed in other ways.

Topics covered: this document covers the following main topics:

• General platform requirements and issues for Java ES

• General compatibility issues for Java ES

• Installation, upgrade, and uninstallation issues for Java ES in general, the installer and uninstaller, and the Java ES components distributed with the installer and uninstaller.

Because this Release Notes document does not cover issues related to all aspects of component usage, you should also read the component-level release notes for the Java ES components you will be using. See Component Release Notes for a listing of the available component-level release notes.

Revision History

Component Release Notes

All the component specific information appears in the respective component release notes. The following component release notes can be found at http://docs.sun.com/coll/1315.2.

What's New in This Release

To continue adding value for Sun software users, Sun has enhanced existing components and added new components for Java ES 5. The following list summarizes the major enhancements and additions. For more details, see the release notes for the individual components of Java ES.

• A new major version of Directory Server, including a new major version of Directory Proxy Server as a subcomponent

• A new major version of Portal Server

• A new major version of Web Server

• The addition of Sun Cluster Geographic Edition software

• Improved support of Solaris Containers, including installation in both sparse root and whole root non-global zones

• Improved system-wide monitoring capabilities and the addition of a monitoring console

Deprecated and Removed Features

Features Deprecated or Removed in This Release

The following system-wide features of Java ES are deprecated or removed in this release. For information about component-specific features that are deprecated or removed in this release, see the release notes for the appropriate component.

• This release does not support Solaris 8 or Red Hat Enterprise Linux 2.1. When Java ES 2005Q4 was delivered, Sun announced that it would not ship new versions of Java ES for these operating system versions after the 2005Q4 release.

• The communication products are no longer part of the Sun Java Enterprise System entitlement. Sun announced this change in August, 2006.

  The following communication products are no longer available in the Java ES installer. For information about downloading them, see the Sun Java Communications Suite information hub on BigAdmin at http://www.sun.com/bigadmin/hubs/comms.

  • Sun Java System Messaging Server

  • Sun Java System Calendar Server

  • Sun Java System Instant Messaging

  • Sun Java System Communications Express

  • Sun Java System Communications Services Delegated Administrator

Features Deprecated or Removed in Future Releases

The following announcements apply to future releases of Java ES.

• Support for J2SE 1.4 might be removed in the next major release of Java ES.

• Support for Red Hat Linux 3 might be removed in the next major release of Java ES.

• Support for Microsfot Windows 2000 might be removed in the next major release of Java ES.

Issues Resolved by This Release

The table below lists the distribution, installation, and uninstallation issues reported in the Java ES 2005Q4 Release Notes that have been resolved in Java Enterprise System 5. For information about the status of issues reported in past component-level release notes, see the release notes for the current version of the component.

Platform Requirements and Issues

Hardware Requirements by Operating System

The disk space and RAM required to install and use Java ES 5 can vary widely, depending on which components you install on a system. The following values are suggested minimums when installing all components on a single system. For more precise values, add together the values from the release notes for the components you are installing on a system.

Solaris Requirements and Issues

Recommended Solaris Update Levels

Although Java ES 5 is support on all versions of Solaris 9 and Solaris 10 on SPARC and x86 platforms, Sun recommends that you use the following updates:

• Solaris 9: Update 7 (9/04) or newer

• Solaris 10 SPARC: Update 1 (1/06) or newer

• Solaris 10 x86: Update 2 (6/06) or newer

Solaris Software Groups Supportd

Java ES runs on Solaris systems installed using the following Solaris software groups:

• SUNWCXall – Entire Solaris Software Group Plus OEM Support

• SUNWCall – Entire Solaris Software Group

• SUNWCprog – Developer Solaris Software Group

Minimized Installation on Solaris 10 (6331921)

Java ES can also run on a minimized Solaris 10 system installed using SUNWCreq (Core System Solaris Software Group) or SUNWCuser (End User Solaris Software Group), provided you are not installing Sun Cluster or Sun Cluster Geographic Edition.

To install Java ES 5 on Solaris 10 system that has SUNWCreq installed, add these packages:

If you will be using the graphical (GUI) installer, also add these packages:

Java ES has been tested with the two minimized Solaris 10 installations listed above. However, it is possible that using certain features of Java ES components may require additional packages.

Required Patch Clusters for Solaris

The Java ES installer checks your system for operating system patches required to run the components you are installing. To avoid failures of these checks during installation on Solaris, Sun offers patch clusters you can download and apply before running the installer. To acquire these patch clusters:

1. Go to http://sunsolve.sun.com.

2. Click “Patches and Updates”.

3. Click “Recommended Patch Clusters”.

4. Locate the patch cluster beginning with “Java ES Required OS” that applies to your OS version and download it.

Note that these patch clusters may contain Solaris kernel patches. Therefore, make sure you:

• Read the README for patch cluster carefully. Also, read the README for each patch in the cluster, especially the kernel patches.

• Install the patch cluster in single user mode, and perform a reconfigure reboot (boot -r) after installation. If some patches fail to install and report that a “reconfigure reboot is needed before invoking additional patch commands”, you need to install the cluster again after the reboot.

Also note that most of the OS patches required by Java ES are already included in recent Solaris updates. Therefore, if you are running a recent Solaris update, you can run the Java ES installer to discover the few patches you need to apply and download them instead of downloading the entire patch cluster.

Linux Requirements and Issues

root is not a valid user on Red Hat Linux 3 update 8 (AS and ES) for x86 (6460658)

When installing Java ES 5 on an x86 system running Red Hat Enterprise Linux 3 update 8, the "root" system user is not recognized.

Solution Before installing Java ES, first install the latest coreutils-4.5.3-28.4.i386.rpm and coreutils-4.5.3-28.4.x86_64.rpm from the Red Hat site.

HP-UX Requirements and Issues

Upgrades and patches required for HP-UX

Before installing, configuring, and running Java ES components on HP-UX, you must install certain software updates and patches. The updates are:

• Transport Optional Upgrade Release (TOUR) 3.1

• GOLDQPK11i(B.11.11.0509.429) Sept 2005 Quality Pack

  • GOLDAPPS11i(B.11.11.0509.429)

  • GOLDBASE11i(B.11.11.0509.429)

The patches are:

• PHSS_30966

• PHCO_29328

• PHKL_25842

• PHNE_29445

These updates and patches are available from the HP IT Resource center, http://itrc.hp.com.

Platform Virtualization Technologies Supported by Java ES 5

Platform virtualization is the ability to run multiple, unrelated guest operating systems in a contained environment on top of shared hardware. Due to the many benefits of platform virtualization, there are a spectrum of virtualization technologies and products available today.

Sun has tested and supports deployments of Java ES 5 on Solaris 10 environments virtualized using the Logical Domains (LDoms) software, which was introduced in Solaris 10 11/06.

LDoms runs on UltraSPARC T1-based and T2-based servers. For information about LDoms, it capabilities, and its requirements, see the Logical Domains documentation collection (http://docs.sun.com/coll/ldom1.0).

If you deploy Java ES components in a supported operating system within a virtualized environment other than LDoms and you encounter a problem, you may be asked to demonstrate the problem in a non-virtualized environment before Sun can respond with service.

As with deployments in non-virtualized environments, you should allocate recommended resources (processor, memory, storage, and so on) to each virtual machine so as to ensure sufficient levels of application performance. See the component documentation for recommended and supported system requirements.

Web Browsers Supported by Java ES 5

Web-based administrative interfaces provided by Java ES 5 components support at least the following web browsers:

• Firefox® 1.0.7 on Solaris 9 and 10, Windows 2000 and XP, Red Hat Linux 3 and 4, and Mac OS X

• Mozilla^TM 1.7.12 on Solaris 9 and 10, Windows 2000 and XP, Red Hat Linux 3 and 4, HP-UX, and Mac OS X

• Netscape^TMCommunicator 7.1 on Solaris 9 and 10, and HP-UX

• Netscape Communicator 8.0.4 on Windows 2000 and XP

• Microsoft Internet Explorer 6.0 SP1 on Windows 2000

• Microsoft Internet Explorer 6.0 SP2 on Windows XP

For information about the web browsers supported by the end user web interfaces provided by Java ES 5 components, refer to the release notes for the component that provides the interface. Release notes for Java ES 5 components are available at http://docs.sun.com/coll/1315.2. Also, see Component Release Notes.

Java Platform, Standard Edition (Java SE) Requirements

On Solaris and Linux, Java Enterprise System is certified with and includes Java SE 5.0 Update 9 (1.5.0_09). On HP-UX, Java Enterprise System is certified with and includes Java SE 5.0 Update 3 (1.5.0_03). Additionally, the following items are compatible with Java SE 1.4.2:

• Shared components

• End user client applications

• Public Java APIs

Specific components might support additional versions of Java SE or might have compatibility issues regarding certain versions of Java SE. For information, see the release notes for the component.

Compatibility Issues

The following subsections describe issues regarding the backward compatibility of Java ES 5 with respect to previous releases of Java ES. Additionally, the issues presented here are those that span multiple Java ES components or that pertain to the Java ES installer or uninstaller. For information about the backward compatibility of a specific component, refer to the compatibility information in the release notes for the specific component. See Component Release Notes for a list of component release notes.

Java SE 5.0 Update 9 is not compatible with Application Server 7 (2137473, 6203688, 6409072)

Java ES 5 is certified with Java SE 5.0 Update 9 (1.5.0_09). If the Java ES installer does not find this version of Java SEon a system, the installer installs this version and makes it available to Java ES components though the symbolic link /usr/jdk/entsys-j2se.

The version of Application Server 7 that shipped with Java ES 2004Q2 makes use of this symbolic link, but is not compatible with Java SE 5.0 Update 9. Thus, Application Server 7 stops functioning correctly after you install Java ES 5 components.

Solution Java ES does not support a mixture of version 2004Q2 and version 5 components on a single system. When upgrading a system from Java ES 2004Q2, you must upgrade all components. If you need access to Application Server 7 during the upgrade process, you can change its configuration to point to Java SE 1.4.2, which was installed with Java ES 2004Q2:

1. Login to Sun Java System Application Server 7 administration console.

2. Update Java settings for the admin server and every application server instance, changing Java Home to point to the Java SE 1.4.2 location. Remember to "Apply Changes" for every instance.

3. Stop all application server instances including the admin server.

4. Modify the asenv.conf file in the config subdirectory of Application Server 7, setting AS_JAVA to point to the Java SE 1.4.2 location.

5. Restart Application Server 7.

Java ES 5 Shared Components are not compatible with previous versions of Instant Messaging (6440340)

After using the Java ES installer to upgrade or install shared components, previous versions of Instant Messaging already installed on the system may no longer function correctly. Symptoms include the failure of the Instant Messaging multiplexor or server to start.

This issue arises because the Sun Java System Instant Messaging and Presence APIs (IMAPI) shared component of Java ES 5 is not compatible with previous versions of Instant Messaging. The Java ES installer installs or upgrades IMAPI in these cases:

• You install Portal Server

• You install Service Registry

• You install or upgrade All Shared Components

Thus, this issue is limited to these cases.

Solution Upgrade Instant Messaging to version 7.2.

Installation Issues

The following information pertains to the installation process using the Java Enterprise System installer.

General Installation Issues

After installing a component with the Java ES installer, you must use the uninstaller to uninstall (no bug number)

If you remove component packages or RPMs directly, the next time the installer is run, it may see a component as still being installed and not behave correctly.

Solution If you have already removed component packages or RPMs manually, you must still use the Java ES uninstaller to uninstall the component.

In CLI mode the Java ES installer continues even when it lacks swap space (6436570)

If the system on which you run the Java ES installer does not have sufficient swap space to run the installer, the CLI mode installer (./installer -nodisplay) continues to run after displaying an error message that includes:

com.sun.entsys.dre.DREException: Not enough space

Solution If you see this message, exit the installer. Then, allocate more swap space or free up existing swap space before running the installer again.

On Solaris 10, installation in a whole root zone is unsuccessful (6451030)

When installing Java ES in a whole root zone on earlier versions of Solaris 10, the installer might display one of these messages:

Unsupported components in zone
Following components required by the selected components, are not 
supported in local zone and they can not be installed directly into 
the local zone. Please install these components from the global zone 
before proceeding the installation

     SharedComponent

or

The Sun Web Console packages that are installed on your system
have a defect that is preventing Java ES from installing in a
while root non-global zone. In order to rectify this situation
you must upgrade the Sun Web Console packages in the global zone
before installing Java ES in a whole root zone. Please see the
Java ES Release Notes (bug 6451030) and Installation Guide for
further information.

Both of these messages appear because the Sun Java Web Console packages already installed contain an incorrect attribute setting that prevents the installer from upgrading them. The Sun Java Web Console packages that contain the incorrect attribute setting were shipped with Solaris 10, Solaris 10 1/06, Solaris 10 6/06, and Java ES 2005Q4.

Solution To resolve this issue, you must upgrade the Sun Java Web Console packages in the global zone before you install Java ES in a whole root zone. You have two options:

• In the global zone, run the installer and install only All Shared Components. This upgrades the Sun Java Web Console packages and fixes the zones attribute, but also installs all the other Java ES 5 shared components into the global zone and propagates them into all non-global zones. This might not be acceptable for your situation and is not recommended if you have a previous version of Java ES installed in a whole root zone.

• In the global zone, upgrade only the Sun Java Web Console packages. To do this, log into the global zone and navigate to the Java ES 5 installation directory for Solaris. As root, do the following:

  cd Product/sunwebconsole ./setup

  The setup script upgrades Sun Java Web Console in the global zone and propagates the upgrade to all non-global zones.

On HP-UX, performance issue with Java ES installer (6472918)

The Java ES installer interacts with the HP-UX depot mechanism to find installed components, check for dependencies, and install the bits. The client-server architecture of the depot mechanism leads to slower system response time, and the repeated interaction makes the overall installation process noticeably slower than on other platforms.

Solution None.

Installer does not report component configuration failures due to a low file descriptor limit (5018734, 6523904)

If the system has a file descriptor limit of set too low, some components cannot be configured correctly. The installer does not report such configuration failures, but the configuration log files show the failures.

Solution Before installation, set the file descriptor limit to a high value, such as 1024 or 2048. After installation, you can reset the file descriptor limit back to its previous value.

Java ES Installer needs a mechanism to query if a product license is of type evaluation (6265136)

The installer should check if shared components is an evaluation component and replace it if in fact it is an evaluation component.

Solution Ensure that the workstation does not have an evaluation component installed before beginning an installation.

Zone improvement and physical media installation (6298792)

Any Java ES 2005Q4 installation using CD swaps from within zones will fail. Installation into non-global zones from CDs is not supported in Java ES 2005Q4. Specifically, installation of Sun Cluster on a local zone is also not supported.

Installer requests patch that is not applicable on Solaris 9, update 6 (6315304)

When installing build 10 on Solaris 9, update 6 the install fails because it requires a patch that is not applicable on update 6 (patch 117714–06).

Solution Install the SUNWced and SUNWcedu packages.

Installation log messages are not always valid (no bug number)

Please note that log messages are not always valid. For example, the “no software was installed” message appears even if some (but not all) component products are installed after an error of some sort.

Auto-selection of components in component selection page confusing (4957873)

When a component product is selected, the installer automatically selects to install any dependent component products. The component product selection page does not indicate that the dependencies have been selected along with the original component product.

Solution None.

Insufficient window width in interface for some locales (4949379)

The window for certain languages like German is not wide enough to display the entire interface. As a result, text of elements like hints get truncated at the right hand side or at the bottom.

Solution Manually resize the window.

Access Manager Installation Issues

On HP-UX, Access Manager installation cannot find gettext binary (6497926)

When installing Access Manager on HP-UX, the installation fails, indicating that Access Manager could not find the gettext binary.

Solution Download getext 0.14.6 or later and install it.

Access Manager SDK configuration causes web server startup failure errors (6293225)

The problem of web server startup failures can be attributed to the Access Manager's SDK configuration. In the current scenario, the AMConfig.properties file contains the wrong information and causes a series a web server startup failures. The following variables do not have the correct information:

• com.iplanet.am.directory.host

• com.iplanet.am.server.host

• com.iplanet.am.console.host

• com.iplanet.am.profile.host

• com.iplanet.am.naming.url

• com.iplanet.am.notification.url

Solution On your node B, where Access Manager SDK is installed with Web Server, modify the <Web_Server_Instance_dir>/config/server.xml file and add the required Access Manager JAR files to the classpath.

Installer doesn't add platform entry for existing directory install (6202902)

The Java ES Installer does not add a platform entry for an existing directory server installation (DIRECTORY_MODE=2).

Solution Edit the platform service Server List attribute to add the second instance. For example. if the first instance is host1.example.com, it will have an entry such as http://host1.example.com:port|01. If the second instance is on host2 and uses the same Directory Server as host1, use the Access Manager administrator console to add an entry such as http://host2.example.com:port|02.

Installing Access Manager on an existing DIT requires rebuilding Directory Server indexes (6268096)

To improve the search performance, Directory Server has several new indexes. Therefore, after you install Access Manager with an existing directory information tree (DIT), rebuild the Directory Server indexes by running the db2index.pl script. For example: # ./db2index.pl -D "cn=Directory Manager" -w password -n userRoot

The db2index.pl script is available in the DS-install-directory/slapd-hostname/ directory.

pre61to62upgrade script does not handle DB based logging correctly (5042233)

After the Access Manager upgrade process from version 6.1 to version 6.2 is finished, the upgrade log indicates that the DB based logging was not handled correctly.

Solution None. The Access Manager upgrade process from version 6.1 to version 6.2 does not support backing up of the DB log tables.

Installing Access Manager With SSL Enabled Directory Server (no bug number)

If Directory Server is already installed and has only LDAPS (SSL) enabled, the installation of Access Manager will fail. To install Access Manager, first enable LDAP (no SSL) for Directory Server. After the Access Manager installation is finished, you can disable LDAP and leave only LDAPS.

Single Quote Not Allowed in Passwords and Root Suffix (no bug number)

In passwords (such as for amadmin) and the Directory Server root suffix, Access Manager does not support a single quote (\q). The back-slash (\\), however, is supported.

Installation of Access Manager fails if Directory Server implements the Reset Password (4992507)

When you run the Java Enterprise System installer, the installation of Access Manager fails if Directory Server is configured to require users to change their passwords the first time they log in.

Solution Set the Directory Server password reset policy to “off”.

Authentication service is not initialized whenAccess Manager and Directory Server are installed on separate machines (6229897)

Although the classpath and other Access Manager web container environment variables are updated during installation, the installation process does not restart the web container. If you try to login to Access Manager after installation before the web container is restarted, the following error is returned:

Authentication Service is not initialized.
Contact your system administrator.

Solution Restart the web container before you login to Access Manager. Directory Server must also be running before you login.

Access Manager does not update the Application Server domain.xml (6439597)

Access Manager does not update the Application Server domain.xml properly with JVM options and server classpath . This is known to occur in the following scenario:

1. You install and configure Application Server and Directory Server.

2. You create a node agent.

3. You create a non-default Application Server instance.

4. You install Access Manager in "Configure Later" mode.

5. You edit the amsamplesilent file and then run it using amconfig.

6. When you try to log in to Access Manager with a browser, an error message is displayed.

Solution Before installing Access Manager, edit the amsamplesilent file so that the container block includes the following information:

AS81_HOME=/opt/SUNWappserver/appserver
AS81_PROTOCOL=$SERVER_PROTOCOL
AS81_HOST=$SERVER_HOST
#AS81_HOST=$DISTAUTH_HOST
AS81_PORT=$SERVER_PORT
AS81_ADMINPORT=$ADMIN_PORT
AS81_ADMIN=admin
AS81_ADMINPASSWD="$ADMINPASSWD"
AS81_INSTANCE=server1
AS81_DOMAIN=domain1
AS81_INSTANCE_DIR=/var/opt/SUNWappserver/nodeagents/nodename/server-instance
AS81_DOCS_DIR=/var/opt/SUNWappserver/nodeagents/nodename/server-instance/docroot
AS81_ADMIN_IS_SECURE=true

After the edits are completed, run the amconfig command:

./amconfig -s amsamplesilent

Application Server Installation Issues

After installing Domain Administration Server, Node Agent is listed as installed and compatible (6379283)

If you install the Application Server Domain Administration Server, the Application Server Node Agent is listed as installed and compatible in subsequent installation sessions. This issue arises because the Domain Administration Server and Node Agent use the same set of packages and differ only in configuration.

Solution None. The software to support node agents is installed. To create a node agent, use the asadmin create-node-agent command. See create-node-agent(1) for more information.

Installer does not recognize host name user enters in configuration page (4931514)

The installer prompts you for the “server name” for the Application Server. However, the installer uses the actual host name of the machine regardless of what you input in the text field.

Solution If the server name is different from the server’s host name, become superuser and type the following in the domain directory of interest (the “server root” directory):

# find . -type f -exec grep -l $HOSTNAME {} \\ ;

Then, change the file contents appropriately.

Cannot start domain on Linux (6396102)

On Linux, attempts to start a domain generate an exception that refers to libstdc++. This occurs because Application Server requires certain compatibility libraries on Linux that are not installed by default.

Solution Install the following compatibility libraries:

• compat-gcc-7.3-2.96.build.i386.rpm

• compat-gcc-c++-7.3-2.96.build.i386.rpm

• compat-libstdc++-7.3-2.96.build.i386.rpm

These libraries are not installed by default, but are available in the Red Hat Linux distribution. Note that the value of build may differ on different versions of Red Hat Linux.

Directory Server Installation Issues

Two versions of Directory Server exist after installation on Solaris 9 (no bug number)

Directory Server 5.1 is bundled with Solaris 9. Therefore, after you install Directory Server from Java ES 5, two versions exist on the system: version 5.1 from Solaris 9, and version 6.0 from Java ES.

When you use Directory Server on such systems, you must make sure you use the command set associated with the version of Directory Server you are trying to administer.

Saving index configuration changes for a suffix generates a null error (6507803)

When accessing Directory Service Control Center through Internet Explorer 6, saving index configuration changes for a suffix causes a null error to appear. Additionally, the progress window for the operation appears to freeze.

Solution Access Directory Service Control Center through a different browser, such as a Mozilla-based browser.

Monitoring Console Installation Issues

Monitoring Console cannot be installed on the same host as other Java ES components (6441664)

The Java ES installer allows you to select any and all components for installation along with the Sun Java System Monitoring Console. However, due a limitation of the Monitoring Console, it does not run when installed on the same host or in the same Solaris zone as the components that it monitors. If Monitoring Console is selected with other components, the installation will not fail, but you will not be able to configure and run the Monitoring Console.

Solution Install the Monitoring Console on a dedicated host where no other Java ES components are installed. When running the installer, do not select the Monitoring Console for installation when installing other components. For more details, see the procedure To Install the Monitoring Console with the Java ES Installer in Sun Java Enterprise System 5 Monitoring Guide.

Alternatively, you can install the Monitoring Console on the same physical machine as other Java ES components by creating a dedicated logical host in a local zone with the Solaris 10 operating system. For more details, see the procedure To Install the Monitoring Console in a Solaris Zone in Sun Java Enterprise System 5 Monitoring Guide.

If you wish to install Java ES components on a host where you previously installed and configured Monitoring Console, follow the procedure To Unconfigure the Monitoring Console in Sun Java Enterprise System 5 Monitoring Guide

Monitoring Console must be installed in the default location (6471270)

When the Monitoring Console is not installed in the default location, it cannot be found by the Web Console and therefore cannot be launched.

Solution Do not specify a location other than the default when installing Monitoring Console.

Installer does not configure the Monitoring Console automatically (related to 6488160)

After installing the Sun Java System Monitoring Console, the Java ES installer does not automatically configure and start the Monitoring Console.

Solution You must manually run the commands to configure and start the Monitoring Console after installation. See the procedures for Installing the Monitoring Console in Sun Java Enterprise System 5 Monitoring Guide, and then the procedure Starting the Monitoring Console in Sun Java Enterprise System 5 Monitoring Guide.

Portal Server Installation Issues

Cannot log in to Mobile Access after installation (6437280)

The problem occurs because the filter entry for the AMLControllerFilter filter is commented in the web.xml file of the Access Manager web application.

Solution In the web.xml file of the Access Manager web application, uncomment the AMLControllerFilter filter entry.

Portal Server configuration appears to hang: progress bar does not change (6350387)

As Portal Server is being configured, the installation progress bar does not move. This can give the impression that the configuration process has hung.

Solution Ignore the apparent inactivity and wait for the Portal Server configuration process, which can take up to 45 minutes on a low-end system, to complete.

(Solaris and Linux) Portal Server upgrade failing — cannot find /opt/SUNWappserver7/bin/asadmin (6313972)

Solution Refer to the following publication for the latest upgrade documentation regarding this issue:

Sun Java Enterprise System 5 Upgrade Guide for UNIX

Help file link does not work for iFrameprovider on the desktop (6199105)

Clicking on the help icon from the SampleIFrame Channel produces “HTTP Status 404 — /portal/docs/en/desktop/iframechann.htm” is not available.

Solution None. No help is provided with iFrame provider.

Installation and uninstallation of Portal Server appears to hang (5106639)

During installation and uninstallation of Portal Server, the installer and uninstaller appear to hang. The delay can be up to 30 minutes before installation/uninstallation finishes successfully.

Solution None.

Sun Cluster Installation Issues

x86 machines running Solaris 10 fail to come up in cluster mode (6299971)

x86 machines running Solaris 10 fail to come up in cluster mode due to changes made for the Solaris boot architecture project. The following error messages are displayed when the machine boots up:

Use is subject to license terms.
NOTICE: Can't open /etc/cluster/nodeid

NOTICE: BOOTING IN NON CLUSTER MODE
NOTICE: NO PCI PROP
NOTICE: NO PCI PROP
Configuring devices.
Hostname: pvyom1
devfsadm: minor_init failed for module /usr/lib/devfsadm/linkmod/SUNW_scmd_link.so
Loading smf(5) service descriptions: 24/24
/usr/cluster/bin/scdidadm: Could not load DID instance list.
Cannot open /etc/cluster/ccr/did_instances.
Not booting as part of a cluster
/usr/cluster/bin/scdidadm: Could not load DID instance list.
Cannot open /etc/cluster/ccr/did_instances.
Note: path_to_inst might not be updated. Please 'boot -r' as needed to update.

Solution Perform these steps:

1. Add /etc/cluster/nodeid to /boot/solaris/filelist.ramdisk.

2. Enter these commands:

   # bootadm update-archive # reboot -- -r

Unable to form a 16-node cluster when all nodes are booted up at the same time (6320429)

Attempting to boot up all nodes of a 16 node cluster at the same time results in node panics and nodes hanging waiting for quorum.

This bug was caused due to incorrect configuration of the private interconnect switches. It is required to disable spanning tree for the switch ports used for the Sun Cluster private interconnects. This was not done for the switches on the 16 node cluster and hence this bug. The cluster cannot be brought online due to this bug.

In order to resolve this issue it is required to disable the spanning tree for the switch ports used for the Sun Cluster private interconnects.

Solution None.

Warning message is displayed for Sun Cluster localized package installation (6338473)

While installing Sun Cluster localized packages, the following warning message is displayed in the Java ES installation log. Localized packages are named SUNW*scspmu. This warning message does not appear when localized components are not selected to install.

Warning: smreg is obsolete and is preserved only for
compatibility with legacy console applications. Use wcadmin
instead.

Type "man wcadmin" or "wcadmin --help" for more information.

This warning is generated because Sun Cluster localization packages use the smreg command instead of wcadmin which is a new command in Sun Java(TM) Web Console 3.x. This message could mislead customers by implying that they need to perform another step to complete the Sun Cluster installation.

Solution This warning does not result from an installation error. You can safely ignore this warning message.

Sun Cluster HA Application Server Agent does not support Application Server 8.1 and HADB 8.1 (6212333)

The installer gives you the option of choosing to install the Sun Cluster HA Application Server Agent with Application Server and HADB 8.1. However, the HA Application Server Agent does not support Application Server and HADB 8.1. As a result, you cannot configure HA Application Server.

Solution Do not install the HA Application Server Agent with Application Server and HADB 8.1.

Sun Cluster Data Services for previous versions of Directory Server (no bug number)

Java Enterprise System 2005Q1 includes the Sun Cluster Data Service for the Sun Java System Directory Server 5 2004Q2. If you need the Sun Cluster Data Service for Sun Java System Directory Server 5.0 or 5.1 or for Netscape HTTP, version 4.1.6, it is available in the Sun Cluster 3.1 Data Services 10/03 release. To request this release, contact your Sun customer service representative.

Sun Cluster Data Service for Oracle Parallel Server/Real Application Clusters not installed from Sun Cluster 3.1 CD (no bug number)

Instead, it is installed from the Java Enterprise System 1 Accessory CD, volume 3. Also, the data services are not installed from the agents CD. Instead, they are installed from the Java Enterprise System 1 Accessory CD, volume 3.

Installer does not allow for additional Sun Cluster agents to be installed if one exists on system (no bug number)

If you have installed a Sun Cluster Agent prior to running the Java Enterprise System installer, the installer does not allow you to install additional agents.

Solution Install additional Sun Cluster Agents using pkgadd.

Web Server Installation Issues

Web Server installation fails if install directory is populated with files from a previously installed version (no bug number)

Solution Back-up all your configuration files. Then, remove the install directory before installing Web Server using the Java Enterprise System installer.

Upgrade Issues

The Sun Java Enterprise System 5 Upgrade Guide for UNIX provides instructions for upgrading to Java ES 5 on the Solaris and Linux platforms. The issues in the following sections describe situations that are not covered in the Upgrade Guide, and so should be used only in conjuction with the Upgrade Guide and not as a replacement for it.

Both the Upgrade Guide and the issues in the following sections refer to Java ES releases by release version and release number. The following table shows how release versions and release numbers are related:

Itemized Upgrade Issues

Localization packages for Access Manager, Application Server, and Message Queue are not upgraded by the installer (6446805)

When upgrade Access Manager, Application Server, or Message Queue, the installer does not upgrade the localization packages even if you choose the "Install multilingual package(s) for all selected components" option.

Solution Remove existing localization packages before upgrading, using the instructions provided in the Sun Java Enterprise System 5 Upgrade Guide for UNIX.

JSP compilation errors in Application Server after other components are upgraded to Java ES 5 (6388329)

After upgrading any Java ES component to Java ES 5 on a system running Release 3 or Release 4 Application Server (version 8.1), Application Server reports errors when you compile JSP pages.

Solution Upgrade Application Server to Java ES 5, or apply the following patch to Application Server 8.1:

• On Solaris: 119166–17

• On Linux: 119168–17

On Linux, applications deployed to Application Server throw Java.security.AccessControlException after other components are upgraded to Java ES 5 (6517722)

After upgrading a Java ES component to Java ES 5 on a Linux system running Application Server, attempts to start some deployed applications throw Java.security.AccessControlException. This problem arises because the location of antchanged in Java ES 5

Solution Upgrade Application Server to Java ES 5, or follow these steps:

1. In Application Server's config/asenv.conf file, change the value of AS_ANT_LIB from "/opt/sun/lib" to "/opt/sun/share/lib".

2. Restart Application Server.

Upgrading Portal Server 7.0 deployed to Web Server follows an unconventional sequence (6507069)

When upgrading Portal Server IFR (Interim Feature Release) 7.0 2005Q4 deployed in Web Server, you must upgrade components in a nonstandard sequence. See the Sun Java Enterprise System 5 Upgrade Guide for UNIX for more information.

Monitoring Framework 1.0 with Instant Messaging needs upgrading if enabled (6515859)

If you enabled the monitoring functionality of Instant Messaging in Java ES 2005Q1 or 2005Q4, you will need to manually upgrade your properties file after you upgrade to Java ES 5.

Solution After you have upgraded your Instant Messaging instance on a given host, edit the new mfwk.properties file to include the configuration parameters you wish to preserve from your old agent.properties file.

Monitoring Issues

This section describes the known issues in the Monitoring Console and in the Monitoring Framework. The Monitoring Framework is a shared component that is automatically installed with other components to enable monitoring.

Patches Required for Monitoring

The following patches are required to prevent certain known issues in the Monitoring Framework. These patches are normally included in other patch bundles required for Java ES or in updated versions of the Solaris operating environment. However, you should verify the existence of these patches or their replacements on any host where you will monitor a Java ES product component:

For the HP-UX operating system, the patches required for monitoring are included among those described in HP-UX Requirements and Issues.

Monitoring Console Interface Issues

New host certificate is not displayed for verification (6467360)

When adding a new host to be monitored, the Monitoring Console uses SSL to secure the connection, but does not show the certificate presented by the selected host. Because the Monitoring Console transmits the host's root password to the node agent, there is a vulnerability to an attacker forging the IP address of the intended host and receiving the password. The risk of this happening is very low because most node agents run on hosts already within a secure network.

Solution If your node agent hosts are not within a secure network, you should verify their authenticity before adding them as new hosts in the Monitoring Console. To verify the authenticity of a host, log in to the host and make sure you recognize its configuration and its file system. For a UNIX host, you can log in with ssh to view the certificate information.

Application Server refers to application instance (6495539, 6388513)

Objects contained in a product are referred to in Monitoring Console as an “application server.” This terminology should not be confused with Sun Java System Application Server.

Solution In the context of the Monitoring Console, an application server refers to the running instance of an installed Java ES component.

Slow response time in Monitoring Console (6490794, 6438443)

Displaying and switching pages in the Monitoring Console can take up to 30 seconds in some cases.

Solution Run the Monitoring Console on a powerful host with no other applications.

Monitoring Console does not display host or domain names (6444357, 6446325, 6496542)

Labels in the left-hand tree do not include host or domain names, only component names. This can make it difficult to identify similar components on different hosts. Similarly, when creating a monitoring rule and selecting the monitored component, instances of the same component on different hosts may be indistinguishable.

Solution Look for host identifiers in the detailed views of the monitored component. Some components include their process ID in their instance name, so you need to know the process ID of the instance on each host.

No simple way to disable monitoring of a particular component (6446505)

The Monitoring Console cannot enable or disable monitoring on a per-component basis.

Solution You must enable and disable the monitoring of a component through each component's own mechanism. For instructions, see the component–specific sections in Chapter 2, Enabling and Configuring the Monitoring Framework, in Sun Java Enterprise System 5 Monitoring Guide.

Console does not always reflect when a monitored component is stopped (6487785)

When a monitored component crashes or is stopped normally, its monitored objects may not be removed from the node agent and remain visible in the left-hand tree of the Monitoring Console. Similarly, if you stop an entire node agent, the host node may not be removed from the left-hand tree. This issue occurs intermittently.

Solution When you stop or restart a server instance, you may need to restart the node agent, the master agent and the Monitoring Console. If you stop a host and its node agent, you may need to restart the master agent and the Monitoring Console. The procedure To Restart a Node Agent in Sun Java Enterprise System 5 Monitoring Guide describes how to do both.

Monitoring rules and alarms are not deleted with their host (6474032)

When a host is removed from the Monitoring Console, the monitoring rules and alarms associated with its monitored components are not deleted automatically. This allows persistency of the rules and alarm states if you add the same host again.

Solution If you do not plan on adding that host again, use the Rule dialog to find and delete all rules associated with the host. Alarms that exist when the host is removed may be acknowledged but will remain in the Monitoring Console because the monitored attribute that triggered the alarm can no longer be accessed. To avoid leaving alarms in the acknowledged state, resolve all alarm conditions in a monitored component and acknowledge the alarms in the Monitoring Console before removing the host.

Less Severe Monitoring Console Issues

The following list tracks other known issues with the Monitoring Console.

6366190

Various tables are not sorted by default

6375583

Host linked from “Objects Using This Installed Product” should not be unknown object

6388558

Using the AppServer plug-in, the “objects contained by this server” should not include children of children

6390983

Enable and disable functionality is not working correctly in the table of hosts

6396891

Caption and description fields displayed for Statistics and Settings objects but not for base objects

6495587

Selecting an object and clicking on Monitoring Rule->New should not require the user to select the object again

6405363

The names of JVM objects listed for a given host are inconsistent

6405949

CMM_Cluster objects created by Application Server are not displayed anywhere

6412408

List of observable objects in the New Rule dialog is not clear

6429231

Object and Operational Status of Portal, Web, and Application Server objects display as unknown

6388513

Enterprise Java Beans deployed in Application Server should have more descriptive names

6434184

The names of attributes in Application Server monitoring objects are impossible to use

6434241

Internal Application Server configuration changes not reflected in the Monitoring Console

Monitoring Framework Issues

Linux IPv6 loopback interface not supported (6356355)

On a Linux system, the Monitoring Framework will not work when IPv6 is enabled. As a result, the instrumentation of your monitored components on this system will not be loaded into the cacao container, and you will not see them in the Monitoring Console.

Solution There are two possible solutions:

• Configure the Monitoring Framework to not use the loopback interface:

  1. In the Monitoring Framework configuration directory (default /etc/opt/sun/mfwk/config), make a copy of the sample properties file:

     cp mfwk.properties.sample mfwk.properties

  2. Set the following parameter in the newly copied mfwk.properties file:

     mfwk.multicast.disableloopback=true

  3. Restart the node agent, the master agent, and the Monitoring Console with the procedure To Restart a Node Agent in Sun Java Enterprise System 5 Monitoring Guide.

• Or disable IPv6 on Red Hat 3.0 with the following steps:

  1. Find this line if it appears in the /etc/modprobe.conf file:

     alias net-pf-10 ipv6

  2. Change it or add the following line:

     alias net-pf-10 off

  3. Reboot the system. IPv6 should now be disabled.

  On Red Hat 4.0, follow the same procedure using the /etc/modules.conf file.

Undeploying a monitored component from a node agent can cause a deadlock (6481273)

In the process of disabling a monitored component, it should be undeployed from its node agent, but this sometimes freezes. Specifically, the cacaoadm undeploy command never returns and monitoring is blocked in the entire node agent.

Solution Kill the process and restart the node agent, the master agent, and the Monitoring Console with the procedure To Restart a Node Agent in Sun Java Enterprise System 5 Monitoring Guide.

C components have slow monitoring performance on Linux (6332884)

Components that rely on C libraries to interface with the Monitoring Framework may display more slowly in the Monitoring Console when they run in the Linux operating environment.

Solution None.

C components may have slower monitoring performance after node operations (6410218)

Components that rely on C libraries may exhibit slower monitoring performance in the Monitoring Console after other components in the same node agent are redeployed or terminated.

Solution Restart the node's Common Agent Container including the node agent, then restart the master agent and the Monitoring Console with the procedure To Restart a Node Agent in Sun Java Enterprise System 5 Monitoring Guide.

C components do not communicate securely with the node agent (6405037)

Inter-process communication between components that rely on C libraries and the node agent on the same host is not secure. By default, communication uses the loopback interface, thereby reducing the security risk.

Solution None.

Java component have slow SNMP performance (6437945)

Components that rely on Java libraries to interface with the Monitoring Framework may experience performance issues when accessed through SNMP.

Solution None.

Node agent cannot discover monitored components on Solaris 9 (6504230)

Due to a bug in Solaris 9, packets addressed to an IPv4 address are not delivered to listener on an IPv6 socket. This interrupts the discovery mechanism between node agents and the components to be monitored on that host.

Solution Force the node agent's JVM to listen on IPv4 sockets with the following commands:

cacaoadm stop
oldvalue=`cacaoadm get-param java-flags --value`
cacaoadm set-param java-flags="${oldvalue} -Djava.net.preferIPv4Stack=true"

Then restart the node agent, the master agent, and the Monitoring Console with the procedure To Restart a Node Agent in Sun Java Enterprise System 5 Monitoring Guide.

Unsynchronized clocks prevent adding a host to the Monitoring Console (6487357)

If the time on the node agent and master agent hosts is too far out of sync, adding that node in the Monitoring Console will fail. The error log of the master agent's Monitoring Framework will report a severe error “during JRMP connection establishment.”

Solution Set the time on either host so they are synchronous.

Documentation of private C API not supported (6463023)

Documentation for a private C API was inadvertently included in the run-time packages. The interfaces it describes are private and subject to change at any time, therefore their use is discouraged.

Solution None.

HP_UX: excessive concurrent monitoring rules causes exception (6481758)

When many monitoring rules are created in parallel in a node agent on the HP-UX operating system, thread numbers in the Java Virtual Machine (JVM) may exceed kernel parameter limits and cause an OutOfMemory exception.

Solution Download and run the HPjconfig tool, as described in the procedure To Optimize Kernel Parameters for Monitoring Framework on HP-UX in Sun Java Enterprise System 5 Monitoring Guide.

Uninstallation Issues

Access Manager Uninstallation Issues

The Access Manager monitoring module is not unregistered during uninstallation (6360971, 6369681)

When uninstalling Access Manager, its monitoring module descriptor is not unregistered.

Solution Use cacaoadm to unregister the com.sun.cmm.am descriptor:

1. Confirm the presence of the com.sun.cmm.am descriptor:

   # cacaoadm list-modules List of modules registered: com.sun.cacao.agent_logging 1.0 ... com.sun.cmm.am 1.0 ...

2. Unregister the descriptor:

   # cacaoadm unregister-module com.sun.cmm.am.xml

3. Restart cacao:

   cacaoadm restart

4. Confirm that com.sun.cmm.am has been unregistered:

   # cacaoadm list-modules List of modules registered: com.sun.cacao.agent_logging 1.0 ...

   (com.sun.cmm.am 1.0 should no longer appear in the list of registered modules.)

Patch Information

For Java ES 5, Sun is adopting a new sustaining model to simplify the task of discovering, downloading, and applying patches to Java ES 5 components. This model consists of two primary features:

• Patch clusters containing the latest appropriate patches for all Java ES components

• Keyword tagging of individual component patches

Patch Clusters. For each platform supported by Java ES 5, you can download a patch cluster containing the latest patches for the versions of components delivered in Java ES 5. These patch clusters are updated on an ongoing basis as components deliver new patches.

To acquire one of these patch clusters:

1. Go to http://sunsolve.sun.com.

2. Click “Patches and Updates”.

3. Click “Recommended Patch Clusters”.

4. Locate the patch cluster beginning with “Java ES Accumulated” that applies to your OS version and processor architecture and download it.

Keyword Tagging. Beginning with the release of Java ES 5, any patch to any component version included in a Java ES release will be tagged in the README file with a keyword indicating that the patch applies to the Java ESrelease. For Java ES 5, the keyword tag is java_es-5. Due to this keyword tagging, you can quickly find all the individual component patches for Java ES 5 using the PatchFinder feature of SunSolve by entering the java_es-5 keyword.

You can also get patches for Java ES 5 on Solaris 10 using Sun Connection. For more information, see http://www.sun.com/service/sunconnection.

Redistributable Files

Some components of Sun Java Enterprise System 5 contain any files that you can redistribute. For information about these files, see the release notes for the components you are using.

Berkeley Database Usage Rights Notice

This product includes object and/or source code for the Berkeley Database, a product of Oracle Corporation. Your use of the Berkeley Database software separately from the Java Enterprise System or authorized derivatives thereof is subject to additional licensing conditions.

Accessibility Features for People With Disabilities

To obtain accessibility features that have been released since the publishing of this media, consult Section 508 product assessments available from Sun upon request to determine which versions are best suited for deploying accessible solutions. Updated versions of applications can be found at:

For more information on Sun's commitment to accessibility, visit

Documentation, Support, and Training

The Sun web site provides information about the following additional resources:

• Documentation (http://www.sun.com/documentation/)

• Support (http://www.sun.com/support/)

• Training (http://www.sun.com/training/)

Searching Sun Product Documentation

Besides searching Sun product documentation from the docs.sun.com web site, you can use a search engine by typing the following syntax in the search field:

search-term site:docs.sun.com

For example, to search for “broker,” type the following:

broker site:docs.sun.com

To include other Sun web sites in your search (for example, java.sun.com, www.sun.com, and developers.sun.com), use “sun.com” in place of “docs.sun.com” in the search field.

Third-Party Web Site References

Third-party URLs are referenced in this document and provide additional, related information.

Sun is not responsible for the availability of third-party web sites mentioned in this document. Sun does not endorse and is not responsible or liable for any content, advertising, products, or other materials that are available on or through such sites or resources. Sun will not be responsible or liable for any actual or alleged damage or loss caused or alleged to be caused by or in connection with use of or reliance on any such content, goods, or services that are available on or through such sites or resources.

Sun Welcomes Your Comments

Sun is interested in improving its documentation and welcomes your comments and suggestions. To share your comments, go to http://docs.sun.com and click Send Comments. In the online form, provide the full document title and part number. The part number is a 7-digit or 9-digit number that can be found on the book's title page or in the document's URL. For example, the part number of this book is 819-4893.