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

Jakarta Patch 8a Hot Fix 4

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

Jakarta Patch 8a Hot Fix 4

The Jakarta Patch 8a Hot Fix 4 release contains fixes to these problems.

For Jakarta Patch 8a Hot Fix 4:
Build date: 06-12-2018_1351
Build tag: glide-jakarta-05-03-2017__patch8a-hotfix4-06-07-2018
Important: For more information about how to upgrade an instance, see Upgrade to Jakarta.

For more information about the release cycle, see the ServiceNow Release Cycle. For a downloadable, sortable version of Jakarta fixed problems, see KB0623655.

Note: This version is approved for FedRAMP.

Fixed problem in Jakarta Patch 8a Hot Fix 4

Problem Short description Description Steps to reproduce




MID Server DefaultUdpTransportMapping thread not reused with use_getbulk use_getscalar options

When SNMP probes run with the use_getbulk or use_getscalar probe parameter set to true, the DefaultUdpTransportMapping thread will not be reused by subsequent SNMP probes with the same parameter(s). This will result in instances of this thread accumulating over time, which will eventually cause the MID Server to be unable to create new threads, requiring the MID Server to be restarted.

The OOB probes with one of the parameters enabled are:
  • SNMP - Switch - BridgePortTable
  • SNMP - Switch - ForwardingTable
  • SNMP - Switch - SpanningTreeTable

Probes without either parameter (or with the parameters, but set to false) will not have this issue. Patterns are also unaffected.

Refer to the listed KB article for details.

Fixes included with Jakarta Patch 8a Hot Fix 4

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