Uploaded image for project: 'Red Hat Process Automation Manager'
  1. Red Hat Process Automation Manager
  2. RHPAM-2476

Fail recovery for asset creation

    XMLWordPrintable

Details

    • Bug
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • 7.5.0.GA
    • None
    • None

    Description

      If after the creation of the asset, we shut down the pod with a breakpoint in this line:

      https://github.com/kiegroup/appformer/blob/a4cf2e727c01a48fdf91ec5dd58f82dc1422913a/uberfire-nio2-backport/uberfire-nio2-impls/uberfire-nio2-jgit/src/main/java/org/uberfire/java/nio/fs/jgit/util/commands/Commit.java#L162

      The asset is never indexed (but it's presented on project explorer and also on git repo)

      Basically, I classify this issue as an edge case and making business central identify that the index is corrupted is a costly resource operation (CPU/RAM).

      Considering also that this issue has a workaround; open the asset on project explorer (user are able to visualize/modify it) and after a save operation the index for that asset is retriggered I propose:

      • Create a new menu on settings like 'Maintance' visible for project owner/admin where the user will be able to retrigger the indexing for that specific project.

      Attachments

        Issue Links

          Activity

            People

              eignatow Eder Ignatowicz
              david.magallanes David Gutierrez
              Tomas David Tomas David
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated: