Uploaded image for project: 'mod-data-export-worker'
  1. mod-data-export-worker
  2. MODEXPW-158

Bulk Edit: FolioExecutionContext is initialized with wrong tenant id if Spring Batch job launches asynchronously in multi tenant cluster



    • Bug
    • Status: Closed (View Workflow)
    • P2
    • Resolution: Done
    • None
    • None
    • Firebird - Sprint 142, Firebird - Sprint 143
    • 1
    • Firebird
    • Implementation coding issue



      Sometimes, if Bulk Edit job launches with async mode in multi tenant environment, FolioExecutionContext is initialized with tenant id other than id of the tenant this job comes from. It causes a try to update a job that does not exist in this tenant.

      Steps to Reproduce:

      1. Go to Bulk Edit and perform edit for users or items.
      2. Create another tenant and do Step 1 at the same time.
      3. Repeat Steps 1 and 2 simultaneously 20 - 30 times.
      4. Go to Export manager and you may see that a couple of jobs have SCHEDULED status.
      5. Retrieve logs for mod-data-export-spring and you may see ERROR like Update for unknown job: job id
      6. Retrieve logs for mod-data-export-worker and you may see the following ERROR:
      java.lang.IllegalArgumentException: count must be greater than zero

      Expected Results:

      No mentioned errors in the log, no jobs with SCHEDULED status in multi tenant cluster.

      Actual Results:

      Jobs are getting stuck with SCHEDULED status, errors in the log.

      Additional Information:

      This bug appears only in multi tenant environment and less often than it was for CIRCULATION LOG.

      Interested parties:

      TestRail: Results


          Issue Links



                Oleksandr_Bozhko Oleksandr Bozhko
                Oleksandr_Bozhko Oleksandr Bozhko
                0 Vote for this issue
                4 Start watching this issue



                  TestRail: Runs

                    TestRail: Cases