Uploaded image for project: 'Hippo CMS'
  1. Hippo CMS
  2. CMS-13760

HippoServiceRegistry doesn't control individual failures for trackerHolders

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Normal
    • Resolution: Fixed
    • None
    • 13.4.4, 14.3.0
    • None
    • None
    • Pulsar
    • Pulsar 241 - Site Dev APIs 1

    Description

      When a module is registered as a ServiceTracker, it never gets executed if another ServiceTracker of the same service, fails before.

       

      This is the code where there is no try-catch inside the for loop, so if any trackerHolder fails, the following trackerHolders won't be executed.

      for (final ServiceHolder<ProxiedServiceTracker> trackerHolder : trackersList) {
          Thread.currentThread().setContextClassLoader(trackerHolder.getClassLoader());
          trackerHolder.getServiceObject().serviceRegistered(serviceHolder);
      }

      Attachments

        Activity

          People

            Unassigned Unassigned
            eperez Eduardo Perez (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: