vFabric Suite 5.1 Release Notes
vFabric Suite 5.1 | 22 MAY 2012
What's in the Release Notes
The release notes cover the following topics:
What's New in vFabric Suite 5.1
This VMware® vFabric Suite™ release includes the following enhancements and new features:
- New name, VMware vFabric Suite(formerly VMware vFabric Cloud Application Platform).
- Existing VMware products added to vFabric Suite: vFabric Application Performance Manager (with vFabric AppInsight), vFabric Application Director, vFabric Postgres (Standard Edition).
- New vFabric product added to vFabric Suite: vFabric Administration Server.
- Support for RedHat Enterprise Linux 6. See Supported Platforms and Configurations.
- Support for Java SE 7. See Supported Platforms and Configurations.
- New features in vFabric License Server 1.1.0:
- Relocated installation procedures (Red Hat Enterprise Linux users only): Detailed procedures for installing vFabric repositories and the vFabric RPM packages have been moved from Getting Started with vFabric Suite to the RHEL installation sections of the individual component documentation. Getting Started with vFabric Suite retains a RHEL walkthrough example.
- New features for each component; see the Release Notes for the components:
Note for vFabric Application Director Users
vFabric Application Director 1.0 users must download and install the VMware vFabric Application Director Activation Key to activate the product during installation. This key is different from the vFabric Suite license key, which does not activate Application Director.
See Download VMware vFabric Application Director 1.0 for details.
The following problems exist in this release of vFabric Suite and are labeled by their ID. Where possible, a workaround is provided.
Also see Oracle JDK 1.6.0_29 Issue for a bug in a specific version of Oracle JDK that affects vFabric License Server reporting commands.
||When performing an upgrade on a vFabric Spring Insight installation from an RPM file, answering No to the Do you accept the VMware license terms? prompt removes the vFabric EULA and tc Server RPMs.
VMware highly recommends that you do not answer No to the licensing question; doing so will make your existing tc Server installation unusable.
Workaround: Reinstall tc Server.
||When upgrading a vFabric Hyperic installation from an RPM file using yum upgrade on RHEL, the process hangs and you have to Control-C to exit. Subsequently, the yum command operates as if the latest version of Hyperic is installed, even though you cannot actually start the Hyperic Server.
VMware highly recommends that you do not upgrade vFabric Hyperic using RPMs at this time.
Workaround: Remove the existing vFabric Hyperic installation and restore all the files from a backup.
||In certain circumstances (described below), the vFabric License Client that is integrated in a vFabric Web Server instance fails to release its vFabric Suite license on shutdown of the Web Server instance. After about 4 hours, the vFabric License Server detects that the Web Server instance has stopped and will release the license.
This issues applies only to vFabric Web Server instances that use a vFabric Suite license (i.e. not local licensing) and are configured with the default_mpm="prefork" option. The 5.1 version of the newserver script does not give you the option to set this flag, although in 5.0 it did.
Workaround: Edit the INSTANCE-DIR/conf/startup.properties file and change the value of the default_mpm variable to worker.
||The vFabric license-usage reports, by default, use the 64-bit JRE installed with vCenter Server. The installer adds the JRE to the end of the path in the Windows command-line tools, current-usage.bat, current-versions.bat, usage-over-periods.bat, and versions-over-periods.bat. If you have a 32-bit JRE in your path, you get an error, because the commands require a 64-bit JRE.
Workaround: Change the SET PATH line in each license report .bat file to:
SET PATH=C:\Program Files\VMware\Infrastructure\jre\bin;%PATH%
||vFabric License Server is not correctly counting CPU/cores on Windows XP/2003 computers.
||If you run vFabric License Server license-usage reports and filter or group by clusters, the output may include VMs that are hosted by ESX hosts that were removed from the cluster but not moved into a new cluster.
||On RHEL when installing Hyperic Server from an RPM file, if you set the HQ_SERVER_INSTALL_PATH variable of the vfabric_hyperic_server.properties file to any value other than the default /opt/hyperic value, the post-installation configuration of Hyperic Server fails.
Workaround: Always install Hyperic Server in the default /opt/hyperic directory by setting the HQ_SERVER_INSTALL_PATH property to this default value.
||If you shut down the ESX host that is running the VMs on which you have installed vFabric components, in certain circumstances not all vFabric licenses are released.
||When you start many GemFire cacheservers, in certain circumstances a cacheserver node takes more than 30 seconds to read information from the vFabric License Server. Because 30 seconds is the default timeout when cacheserver nodes start, the nodes end up using the default evaluation vFabric license. The evaluation license in turn allows a maximum of only three nodes to be started, and thus any new nodes that default to the evalulation license because of this issue will fail.
||On RHEL, the RPM install of vFabric GemFire fails if you have not previously installed a JDK or JRE on the VM.
Workaround: Before installing GemFire from RPM, install a JDK or JRE on the VM.
||When you install vFabric Hyperic Server from RPM on RHEL, and the installation process is scrolling through the EULA, the scrolling process occasionally hangs for long enough that you might think there is a problem, even though the installation will continue successfully after awhile.
Workaround: Wait until the installation starts again.
||If a vFabric license expires while a component is using it, the license assignment is not expired.
||If a vFabric license is deleted while the component that has consumed it is still running, the vFabric License Server expires the license from the license table but the license assignment is not expired.
||No Content-Type header is returned in the response to GET /vfabric/v1/agent-image/content.
||The API permits a tc Server instance that uses a Tomcat 6.0.x runtime to be created, but the 6.0.x runtime is not supported.
Oracle JDK 1.6.0_29 Issue
vFabric License Server reports does not work correctly if you are using JDK 1.6.0_29, due to the Oracle bug 7105007.
The following 5.0 known issues have been resolved in vFabric Suite 5.1.
||The vFabric License Server installer program installs the server in the default location of the vCenter Server (c:\Program Files\), even if vCenter Server is actually installed in a different location. As a result, the vFabric License Server does not work correctly.
||On RHEL, if you use the rpm -e command to remove the GemFire RPM, the command does not also stop the cacheserver if it is currently running.
Workaround: Stop the cacheserver yourself before you remove the GemFire RPM using rpm -e.
||When you uninstall the vFabric License Server using the installer program, the initial focus is on the Back button instead of the username/password field. (Closed because feature works as designed.)
||When you uninstall vFabric License Server using the installer program, the vCenter username/password dialog box shows up in the background instead of the foreground. (Closed because feature works as designed.)
||When you uninstall vFabric License Server using the installer program, if you click the Cancel button on the vCenter Server username/password dialog, the uninstall continues to delete files and completes successfully rather than stopping and leaving the License server running.
||When you uninstall vFabric License Server using the installer program, it does not remove the database the License Server was using to store its metadata. This is correct behavior in an upgrade, but if you plan never to use the License Server again, you must manually remove the database. (Will not fix)
||The SQLServer driver included in vFabric License Server does not support integrated authentication. (Will not fix - note added to the installation documentation.)