Uploaded image for project: 'AppFormer'
  1. AppFormer
  2. AF-2061

Indexing failed during importing one sample project [CAT1]

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • None
    • None
    • None
    • 2019 Week 20-22, 2019 Week 23-25, 2019 Week 26-28, 2019 Week 29-31, 2019 Week 32-34, 2019 Week 35-37, 2019 Week 38-40 (from Sep 16)
    • NEW
    • NEW

    Description

      I created an empty space "sample-01" and then I tried to import sample project called "Course_Scheduling". After a while (around 30 seconds) I got dialog about indexing failure. And an empty project without an asset was opened. In bottom error line I saw the indexing failure message (see screenshot).
      I tried to import another sample project and import ends successfully and assets are visible on all pods I'm log to.
      After 5 minutes I saw assets in BC on pod where I import sample project. These assets are only visible on this one pod.

      I attached all BC logs.

      Attachments

        1. 2019-05-15-screen1.png
          2019-05-15-screen1.png
          66 kB
        2. 2019-05-15-screen2.png
          2019-05-15-screen2.png
          133 kB
        3. 6l22b.log
          422 kB
        4. crffj.log
          183 kB
        5. k6zkj.log
          884 kB

        Issue Links

          duplicates

          Bug - A problem that impairs or prevents the functions of the product. JBPM-8419 Indexing has not finished - org.apache.lucene.store.LockObtainFailedException

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Resolved

          Bug - A problem that impairs or prevents the functions of the product. RHPAM-2084 Unable to open projects in business-central due to LockObtainFailedException on Windows

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed
          is related to

          Bug - A problem that impairs or prevents the functions of the product. AF-2184 On one BC pod are displayed Unexpected error with every asset lock and unlock

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. RHPAM-2130 Space is not visible after creation on OpenShift

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              aparedes@redhat.com Adriel Paredes
              jakubschwan Jakub Schwan
              Tomas David Tomas David
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: