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

uploading a dependency with same GAV via business central the 2nd time sometimes cause data corruption

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Major Major
    • None
    • 7.1.1.GA
    • Business Central
    • Hide

      1. create a simple project with one simple java pojo class called TestDependency.
      2. upload it to rhpam via the business-central.
      3. create a project from business-central and add the uploaded project in step #2 as one dependency.
      4. add a process that import the dependency and reference the dependency in a script task.
      TestDependency test = new TestDependency();
      test.testMethod();
      5. build&deploy the project.
      6. everything is fine so far.
      7. make slight change in the dependency project created in step #1 and rebuilt it.
      8. upload it to rhpam via business-central.
      9. rebuild/deploy the project created in step #3. It failed with error "DependencyTest cannot be resolved to a type".

      Show
      1. create a simple project with one simple java pojo class called TestDependency. 2. upload it to rhpam via the business-central. 3. create a project from business-central and add the uploaded project in step #2 as one dependency. 4. add a process that import the dependency and reference the dependency in a script task. TestDependency test = new TestDependency(); test.testMethod(); 5. build&deploy the project. 6. everything is fine so far. 7. make slight change in the dependency project created in step #1 and rebuilt it. 8. upload it to rhpam via business-central. 9. rebuild/deploy the project created in step #3. It failed with error "DependencyTest cannot be resolved to a type".
    • 2019 Week 08-10, 2019 Week 11-13, 2019 Week 14-16, 2019 Week 17-19

      If a dependency jar is uploaded a 2nd time to buisness central (with the same GAV), no error is given. But any successive use of the dependency (like trying to Build a kjar of Assets) results in the error "Unable to read file" or "xxx cannot be resolved to a type".
      It seems that the uploading of the dependency causes the corruption.

      This issue can't be reproduced consistently. It occurs sporadically.

      One workaround I've found is, when this happens I remove the .index folder and restart the server then everything works back to normal.

              mdessi-1 Massimiliano Dessi
              rhn-support-ghu Gary Hu
              Barbora Kapustova Barbora Kapustova
              Barbora Kapustova Barbora Kapustova
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: