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

Cache problem with dependencies

    XMLWordPrintable

Details

    • 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.

      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.

    Description

      If a dependency jar is uploaded a 2nd time to business 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".
      Sometimes the build fail with just one jar
      Sometimes the build fail because was not able to read the jar even if it's present
      Sometimes the build is successful even the dependencies was just delete from the maven repo
      Sometimes the build is successful with two jars and both are executed
      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,
      the delete of the .index probably force to reload everything.

      The root of the problem seems a cache problem on the compiler pipeline.
      I two jars with the same GAV are uploaded both are executed.

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. RHPAM-1864 uploading a dependency with same GAV via business central the 2nd time sometimes cause data corruption

          • 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

              david.magallanes David Gutierrez
              mdessi-1 Massimiliano Dessi
              Barbora Siskova Barbora Siskova
              Barbora Siskova Barbora Siskova
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: