Uploaded image for project: 'Crowd Data Center'
  1. Crowd Data Center
  2. CWD-2587

FailedEntities in a BatchResult can sometimes be ignored, giving no feedback in the logs

    XMLWordPrintable

Details

    Description

      Certain code paths can cause FailedEntities in a BatchResult to not be logged, for example, consider:
      DBCachingRemoteChangeOperations#addGroups > CachingDirectory#addAllGroups > OfBizGroupDao#addAll, which adds a failure that is ignored.

      Given that BatchResult explicitly provides failedEntities, I would expect #addGroups to handle the failed entities. The current state of affairs means operations with failed entities do not give any feedback to users.

      Attachments

        Issue Links

          blocks

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-25094 Problems when syncing via Crowd Embedded can be silently ignored as no feedback is given in the logs

          • Medium - Medium priority issues
          • Closed
          is cloned from

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-24952 When Syncing with Crowd fails due to a bad user it fails for everyone after that user, this should be more robust.

          • High - High priority issues
          • Closed

          Activity

            People

              aragot AdrienA (Inactive)
              mtan MinanA
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - 6h
                  6h
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 6h
                  6h