Done
Details
Assignee
Volodymyr RohachVolodymyr RohachReporter
Viachaslau KhandramaiViachaslau KhandramaiPriority
P2Story Points
2Sprint
NoneDevelopment Team
FolijetFix versions
Release
Sunflower (R1 2025)RCA Group
Implementation coding issueTestRail: Cases
Open TestRail: CasesTestRail: Runs
Open TestRail: Runs
Details
Details
Assignee
Volodymyr Rohach
Volodymyr RohachReporter
Viachaslau Khandramai
Viachaslau KhandramaiPriority
Story Points
2
Sprint
None
Development Team
Folijet
Fix versions
Release
Sunflower (R1 2025)
RCA Group
Implementation coding issue
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created January 5, 2025 at 2:07 PM
Updated March 13, 2025 at 5:35 PM
Resolved January 17, 2025 at 9:27 AM
The DI_JOB_COMPLETED event, which is expected by mod-bulk-operations, is not being sent by the mod-source-record-manager module upon completion of the data import process:
There is no log entry in mod-source-record-manager logs
regarding the event’s dispatch (https://github.com/folio-org/mod-source-record-manager/blob/8145e17c572630b40bb7519df9b7f8c3e72b44e2/mod-source-record-manager-server/src/main/java/org/folio/verticle/JobExecutionProgressVerticle.java#L281 ). This results in the bulk operation failing to complete successfully because it awaits the DI_JOB_COMPLETED message. The issue has been identified in the artifact #989 of mod-source-record-manager. It can be reproduced on the https://folio-snapshot.dev.folio.org and https://folio-snapshot-2.dev.folio.org environments.
Note: In the local setup (busybee), the event is successfully sent and intercepted by mod-bulk-operations: