Geneva Patch 3 Hot Fix 7 Geneva Patch 3 Hot Fix 7 provides fixes for the Geneva release. For Geneva Patch 3 Hot Fix 7: Build date: 03-09-2016_1350 Build tag: glide-geneva-08-25-2015__patch3-hotfix7-03-08-2016 For more information about how to upgrade an instance, see Upgrade to Geneva. For more information about the release cycle, see the ServiceNow Release Cycle. For a downloadable, sortable version of Geneva fixed problems, see KB0598265. Note: This version is approved for FedRAMP. Fixed problems in Geneva Patch 3 Hot Fix 7 Problem Short description Description Steps to reproduce DiscoveryPRB660591 Async - Discovery sensor jobs causing JVM memory exhaustion on the nodes, Shazzam sensor consuming more memory than usual A JVM memory issue is causing high memory consumption by the Shazzam sensor in Discovery sensor jobs, which causes nodes to recycle/restart. Although Shazzam is working as expected, it is consuming more memory than usual. The following steps may cause this to reoccur: Browse to Discovery > Discovery Schedules. Add the column Shazzam batch size. For all schedulers, change the Shazzam batch size from 500 to 5000. DiscoveryPRB665679 vCenter sensor processing takes several hours for large vCenters vCenter sensor processing can take several hours for extremely large vCenters, and the probe payload can be 25+ MB. Performance needs to be improved and the payload size reduced. Important: The fix for this PRB involves changes to the following customizable scripts for the vCenter sensor: <target_name>VCenterSensor</target_name> <type>Script Include</type> <action>INSERT_OR_UPDATE</action> <target_name>vCenter.getSANStorageInfo</target_name> <type>Probe parameter</type> <action>INSERT_OR_UPDATE</action> <target_name>VMWarevCenterProbe</target_name> <type>MID Server Script Include</type> <action>INSERT_OR_UPDATE</action> If you have customized your vCenter sensor, it will not be upgraded and may still fail during discovery. To ensure that this PRB's fix applies to your vCenter sensor, revert your changes to the OOB version before upgrading. Discover a vCenter with 500 ESX servers, 5000 VMs, 3000 FC ports and 8000 FC disks. Note that vCenter sensor processing lasts for several hours. MID ServerPRB663995 MID server does not process any records because all threads are waiting for SSH session, and command timeout does not work At times, the probe reaper is not interrupting the correct thread upon probe timeout. This causes the worker thread to be stuck there indefinitely. MID ServerPRB664146 SSHSharedSessionCache locks the whole cache when returning session to pool, and Apache Commons Pool swallows exception Apache Commons Pool swallows exception on creation failure, which may cause a dirty session wrapper in our own cache. Fixes included with Geneva Patch 3 Hot Fix 7 * Unless any exceptions are noted, you can safely upgrade to this release version from any of the versions listed below. These prior versions contain PRB fixes that are also included with this release. Be sure to upgrade to the latest listed patch that includes all of the PRB fixes you are interested in. Geneva Patch 3 Hot Fix 6 Geneva Patch 3 Hot Fix 5 Geneva Patch 3 Hot Fix 3 Geneva Patch 3 Hot Fix 2 Geneva Patch 3 Hot Fix 1 Geneva Patch 3 Geneva Patch 1 Hot Fix 6The PRBs in GP1HF6 were also fixed in * GP3, GP4: PRB657730, PRB658175 GP3: PRB658746 Geneva Patch 1 Hot Fix 5 Geneva Patch 1 Hot Fix 2 Geneva Patch 1 Hot Fix 1 Geneva Patch 1 Geneva fixes Note: The fixes for Geneva Patch 2 and Geneva Patch 3 were combined into one patch. ServiceNow documentation refers to this combined patch as Geneva Patch 3. Geneva Patch 3 Hot Fix 4 does not exist.