Yokohama Patch 6 Hotfix 1

  • Release version: Yokohama
  • Updated August 8, 2025
  • 2 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Yokohama Patch 6 Hotfix 1

    The Yokohama Patch 6 Hotfix 1 is a ServiceNow release containing critical fixes addressing several known issues impacting functionality and performance. This update is part of the Yokohama release family and is compatible with prior Yokohama Patch versions. It also marks availability of the ServiceNow AI Platform in Regulated Market environments.

    Show full answer Show less

    Key Fixes

    • Activity Stream: Resolved the issue where Activity Response Generation (ARG) updates were not reflected in the workspace, ensuring ARG changes now appear correctly.
    • Analytics Data API: Fixed an error where drilling down on KPIs in Performance Analytics dashboards incorrectly showed a 'No internet connection' message, improving dashboard usability.
    • Application Manager: Addressed the missing 'My Company Application' page after upgrading Yokohama to restore access to this management interface.
    • Cache Management: Corrected a file handle leak caused by LazyInputStream behavior in LargeContentDiskCache, preventing file descriptors from accumulating and potentially impacting server stability.
    • UX Framework: Enhanced dependency tracing to use LargeContentDiskCache.getMetadata, avoiding unnecessary file descriptor increases on cache hits and improving resource management.

    Upgrade Guidance

    Customers can safely upgrade to this hotfix from any previous Yokohama Patch versions (1 through 6). It is recommended to upgrade to the latest patch to benefit from all included fixes. For detailed upgrade procedures and information on the ServiceNow release cycle, refer to the official ServiceNow documentation.

    Practical Impact

    Applying this hotfix improves system reliability by fixing resource leaks and interface errors, enhances user experience in analytics and application management, and ensures compliance for deployments within regulated environments. These fixes help maintain optimal performance and stability in your ServiceNow instance running the Yokohama release.

    The Yokohama Patch 6 Hotfix 1 release contains fixes to these problems.

    Build information:
    Build date: 08-05-2025_2351
    Build tag: glide-yokohama-12-18-2024__patch6-hotfix1-08-01-2025
    Important:
    For more information about how to upgrade an instance, see ServiceNow upgrades.

    For more information about the release cycle, see the ServiceNow Release Cycle.

    Note:
    This ServiceNow AI Platform major family release is now available in ServiceNow's Regulated Market environments. For more information about services available in isolated environments, see KB0743854.

    Fixed problem

    Problem Short description Description Steps to reproduce

    Activity Stream

    PRB1923345

    		 Activity Response Generation (ARG) updates for workspace are not included in Yokohama ARG changes are missing in workspace.
    1. Set up Activity Response Generation.
    2. Enable the configuration.

    Analytics Data API

    PRB1845187

    KB2238953

    		 Drilling down on KPIs in a Performance Analytics dashboard produces the error 'No internet connection' Drilling down on any value redirects the user to the KPI details page with a 'No Internet connection' error.

    Refer to the listed KB article for details.

    Application Manager

    PRB1924202

    KB2397128

    		 'My Company Application' ($mycompany appsmgmt.do) page isn't found The 'My Company Application' page isn't found after upgrading Yokohama.

    Refer to the listed KB article for details.

    Cache

    PRB1922845

    		 File handlers are left open if a LazyInputStream is closed before being read by LargeContentDiskCache If LazyInput#close is called before the internal StreamSupplier is opened by LazyInput Stream#stream, the InputStream remains open until finalizers are calling during garbage collection. File handles are leaked when using LargeContent DiskCache and only call getMetadata() or contentExists(). Because the supplier is never invoked and the stream is never opened, closing the LazyInputStream doesn't close the underlying FileInputStream. These leaked file handles are only released when the garbage collector runs finalizers.
    1. Start glide.
    2. Run java Process Status (JPS).
    3. Get the Process ID (PID) of the glide process.
    4. Run LSOF.
    5. Take note of the file descriptor entries.
    6. Flush the cache.
    7. Load the Service Operations Workspace home page.
    8. Repeat step 3 through step 6.

    Expected behavior: File descriptor entries is close to the original number.

    Actual behavior: Notice the 10's or 100's of additional file descriptor entries, indicating that the file handlers are left open.

    UX Framework

    PRB1923311

    		 UX dependency tracing should use LargeContentDiskCache. getMetadata to avoid file touching File descriptors should not increase when there is a cache hit.
    1. Access a workspace homepage (for example: CSM, SOW, or Case Record).
    2. Re-load the page multiple times.
    3. Monitor open file descriptors for LSOF.
    4. Notice the file descriptor entries.

    Notice that the file descriptors increase even when there's a cache hit.

    Fixes included

    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.