VMware

vFabric Suite 5.2 Release Notes

vFabric Suite 5.2 | 16 OCT 2012

Last document update: 06 DEC 2012

What's in the Release Notes

The release notes cover the following topics:

What's New in vFabric Suite 5.2

This VMware® vFabric Suite™ release includes the following enhancements and new features:

The following features have changed in vFabric Suite 5.2:

  • New vfabric repository RPM for RHEL. As with each new release of vFabric Suite, if you use Red Hat Enterprise Linux (RHEL), you install a new VMware repository configuration RPM. This new installation enables you to easily browse and install the vFabric component RPMs associated with vFabric Suite 5.2, such as vFabric tc Server 2.8. In addition, the 5.2 repository RPM installation now asks you immediately to accept the End User License Agreement (EULA). In previous releases, you accepted the EULA the first time you installed a vFabric component associated with the Suite release. See RHEL: Example Walkthrough of Installing Component From the VMware RPM Repository.
  • vfabric-all repository deprecated. The VMware RPM repository vfabric-all is deprecated and will no longer be updated with new RPMs. In addition to vFabric Suite components, vfabric-all contained releases of vFabric components that were not associated with a vFabric Suite release. If you want to install a vFabric component that is not yet part of a vFabric Suite release, you must download the RPM from the VMware Download Center and install it using rpm -ivhf. For example, under RHEL: Install vFabric tc Server Standard Edition from an RPM, see "Install vFabric tc Server from a Downloaded RPM."

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.

Known and Resolved Issues

The following problems have been identified in this release of vFabric Suite. Where possible, a workaround is provided.

The table indicates the version in which the problem was found and, where applicable, the version in which it was fixed. If the Fixed In column is blank, it means the problem still exists in the latest version of vFabric Suite.

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.

Issue Number Description Found In Fixed In
VFP-553 If an ESXi host is disconnected, and that host manages VMs on which vFabric components are installed and are licensed by the vFabric License Server, the vFabric licenses on the VMs are correctly unassigned, but do not get automatically reassigned when the ESXi host is reconnected.

Workaround: After the ESXi host is reconnected, restart the vFabric components on any associated VMs.
5.2
VFP-552 If a VM on which a vFabric component is installed migrates to a different ESXi host, and you run the versions-over-periods.bat monitoring command or use the Web User Interface to view license usage reports, the "Maximum Number of Machines" incorrectly increases. 5.2
VFP-549 If you install and start a vFabric component on a VM before you install the vFabric License Server and activate your vFabric license using the vSphere Client, the vFabric License Server does not assign a license to the vFabric component even though it should.

Workaround: Restart the vFabric component.
5.2
VFP-533 If you install two different versions of one of the open-source components that can be tracked by the vFabric License Server (such as Apache Tomcat 6.0.35 and 7.0.29) on the same RHEL VM, the current-versions.bat monitoring command may output incorrect information about the two versions as you start and stop them. This is also true for Apache HTTP Server and open-source RabbitMQ. 5.2
VFP-531 If you install and start open-source (OSS) RabbitMQ on a RHEL VM using a non-RPM package, the vFabric OSS license agent may not detect that the OSS RabbitMQ server is actually running. Thus it may not assign the server a vFabric license, which results in incorrect output when you run the monitoring commands.

Workaround: Install open-source RabbitMQ on RHEL using the RPM package.
5.2
VFP-381 If you run vFabric License Server license-usage reports and filter or group by clusters, the output may include VMs that are hosted by ESXi hosts that were removed from the cluster but not moved into a new cluster. 5.2
VFP-325 If you shut down the ESXi host that is running the VMs on which you have installed vFabric components, in certain circumstances not all vFabric licenses are released. 5.2
VFP-298 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.
5.2
VFP-288 When you install vFabric Hyperic Server from RPM on RHEL, and the installation process is scrolling through the EULA, the scrolling process occasionally hangs long enough that you might suspect a problem. The installation will continue successfully after awhile.

Workaround: Wait until the installation starts again.
5.2
VFP-488, VFP-490 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.
5.1 5.2
VFP-470 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.
5.1 5.2
VFP-465 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%
5.1 5.2
VFP-330 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.
5.1 5.2
VFP-286 If a vFabric license expires while a component is using it, the license assignment is not expired. 5.1 5.2
VFP-282 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. 5.1 5.2
VFP-495 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.

This issue has been closed with status Won't Fix.
5.1 5.2
VFP-422 vFabric License Server is not correctly counting CPU/cores on Windows XP/2003 computers.

This issue has been closed with status Won't Fix.
5.1 5.2
VFP-311 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.

This issue has been closed with status Won't Fix.
5.1 5.2
VMS-1121 No Content-Type header is returned in the response to GET /vfabric/v1/agent-image/content. 5.1 5.2
VMS-1122 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. 5.1 5.2

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.