Details
-
Bug
-
Status: Closed (View Workflow)
-
P2
-
Resolution: Done
-
None
-
-
5
-
Folijet Support
-
Morning Glory (R2 2022) Bug Fix
-
Incomplete/missing requirements
Description
I tried to import all of these files in the PTF env and for the most part got the performance that you all reported here. However, for one file I chose a wrong profile, using the "Default - Create SRS MARC Authority" profile instead of the "Default - Create Instance and SRS MARC Bib" profile. As a result the job got stuck at 0%. I tried to manually stop the job after hours of waiting, then reimported it, but the job still stuck. A new job still stuck after I restarted all the DI modules. Any thoughts on how to get the system working again?
Error message in SRM log:
"org.folio.services.exceptions.RawChunkRecordsParsingException: io.vertx.core.impl.NoStackTraceThrowable: Couldn't update JobExecution status, JobExecution already marked as CANCELLED",lcp2/mod-source-record-manager/1ae241003ae84a55b570501e03f69b5a
All records in srm.journal_records table contain ERROR message: "Couldn't update JobExecution status, JobExecution already marked as CANCELLED".
Expected Results: import job should be completed with errors and there is corresponding error message should be on the logs page.
TestRail: Results
Attachments
Issue Links
- blocks
-
MODSOURMAN-865 Release v3.4.3 (R2 MG bugfix)
-
- Closed
-
- defines
-
UXPROD-3464 NFR: Data Import R2 2022 Morning Glory Support Bug work
-
- Closed
-
- relates to
-
FAT-2827 Review of C359245, C359246, C359247test case
-
- Closed
-
-
MODDICONV-214 Import stops if profiles were incorrectly set-up - DRAFT
-
- Closed
-
-
MODDICONV-226 SPIKE: Mechanism for validating DI profiles
-
- Closed
-
-
MODDICONV-294 Disallow creation of JobProfile containing Update without Match
-
- Open
-
-
MODSOURMAN-940 DI Jobs stuck when selecting a wrong profile
-
- Closed
-