Environment: ========== TIBCO BusinessEvents (BE):5.1.0 All Operating Systems
Symptoms: ========= After installation of BE 5.1.0 HF2 with Universal installer 3.1.0 V4, starting the Hawk agent resulted in the following exception on the console: >>>>>>>>>>>>>> java.lang.NumberFormatException: For input string: "174.1-HF2" at sun.misc.FloatingDecimal.readJavaFormatString(FloatingDecimal.java:1222) at java.lang.Float.parseFloat(Float.java:422) at com.tibco.installer.util.TIBCOUniversalInstallerRegistryInfo.createProductXMLElement(TIBCOUniversalInstallerRegistryInfo.java:492) at com.tibco.installer.util.TIBCOUniversalInstallerRegistryInfo.gatherDeploymentInfo(TIBCOUniversalInstallerRegistryInfo.java:225) at com.tibco.installer.util.TIBCOInstallerUtil.getInstalledTIBCOProducts(TIBCOInstallerUtil.java:130) at com.tibco.installer.util.TIBCOInstallerUtil.getInstalledProductList(TIBCOInstallerUtil.java:669) at com.tibco.tra.tsm.TsmSyncInventory.run(TsmSyncInventory.java:86) <<<<<<<<<<<<<<
When the xml files under /_installInfo, the following HF2 releated xml files have "buildNumber="V174.1-HF2"": >>>>>>>>>>>>>>>> activespaces-admin_2.0.1.044_prodInfo.xml activespaces-common_2.0.1.044_prodInfo.xml be-datagrid_5.1.0.174_prodInfo.xml be-monitoringandmanagement_5.1.0.174_prodInfo.xml be-process-modeler_1.0.0.174_prodInfo.xml be-query_5.1.0.174_prodInfo.xml be-server_5.1.0.174_prodInfo.xml be-studio_5.1.0.174_prodInfo.xml businessevents-hf_5.1.0.002_prodInfo.xml <<<<<<<<<<<<<<<<<
Cause: ========= The expected buildNumber should only have digits in it. This was a mistake on the packaging build to allow the -HF2 in the build number.
Resolution: ========= Change every instance of buildNumber="V174.1-HF2" to buildNumber="V174.1" under TIBCO_HOME/_installInfo/*.xml
There is an outstanding CR REL-175 regarding this issue.