Uploaded image for project: 'Dev - Nexus Repo'
  1. Dev - Nexus Repo
  2. NEXUS-25630

require and add contextual thread names to code using org.sonatype.nexus.scheduling.PeriodicJobService

    Details

    • Type: Improvement
    • Status: New
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 3.28.1
    • Fix Version/s: None
    • Component/s: Support Tools
    • Labels:
    • Notability:
      n/a

      Description

      The interface PeriodicJobService implementation org.sonatype.nexus.scheduling.internal.PeriodicJobServiceImpl uses the name "periodic" to name its threads. The issue is this service is seemingly intended to be a generic service that any code can consume. ( currently rhc, some search and browse features and blob store metrics file updater threads use it ), and as such the thread names it spawns look like periodic-X-thread-XX

      Expected

      Thread names should be named contextually to aid debugging and support efforts.

      Adjust the PeriodicJobServiceImpl so that a consumer of it is forced to specify a custom name, and fix the existing usages of that interface so that the names are contextual ( example names like blobstore-metrics-updater , rhc-repo-check, etc. )

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            plynch Peter Lynch
            Last Updated By:
            Wes Wannemacher Wes Wannemacher
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Date of First Response:

                tigCommentSecurity.panel-title