test

Sun Java Enterprise System 5 Release Notes for UNIX

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:

Thus, this issue is limited to these cases.

Solution Upgrade Instant Messaging to version 7.2.