Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.

Geneva Patch 4 Hot Fix 6

Log in to subscribe to topics and get notified when content changes.

Geneva Patch 4 Hot Fix 6

Geneva Patch 4 Hot Fix 6 provides fixes for the Geneva release.

For Geneva Patch 4 Hot Fix 6:
Build date: 04-15-2016_1853
Build tag: glide-geneva-08-25-2015__patch4-hotfix6-04-15-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 4 Hot Fix 6

Problem Short description Description Steps to reproduce
Platform Performance


Semaphores not loaded into memory on zboot/upgrade until node restart At node startup, we read from the sys_semaphore table and load them into memory. We added a new semaphore for AMB in Geneva that did not get loaded into the memory after the upgrade to Geneva. Now after the upgrade, we trigger an event that reloads all the semaphores into the memory.
  1. Upgrade from Fuji to Geneva.
  2. Go to and check for AMB Semaphores.
Instead of the seeing the expected 4 available AMB semaphores, there are no AMB semaphores.
Platform Performance



ServletTransaction does not account for recycled requests and leaves sessions in session sync The RESTAPIProcessor throws an exception that causes the transaction to be cancelled, but not release the session sync on the session. This results in sessions "leaking" in the queue and can eventually, in a worst case scenario, consume the whole transaction queue. The affected end user(s) experiences HTTP 429 "Rejecting request" errors. The following builds contain the complete fix for this issue:

Refer to the listed Known Error KB article for details, including relief and preventative actions.



When an instance encounters periods of resource stress (multiple long running transactions), the addition of presence requests can cause semaphore queue build up, resulting in 429 error responses A separate semaphore (Presence) has been added to ensure that presence requests cannot cause queue build up. The following are symptoms of this issue:
  • Once an instance gets slow and starts queuing up requests longer than usual, the fact that there are lots of presence requests lead them to fill the queue. This causes all requests after 150 are queued to be rejected with a 429 error response.
  • When requests are rejected, some parts of the user interface (e.g. navigator, activity stream) may be missing. Users may also encounter 429 errors on page requests.

Fixes included with Geneva Patch 4 Hot Fix 6

* 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.