Details
-
Story
-
Status: Closed (View Workflow)
-
P3
-
Resolution: Done
-
None
-
-
Folijet Sprint 133, Folijet Sprint 134
-
3
-
Folijet
-
Lotus (R1 2022) Bug Fix
-
Incomplete/missing requirements
Description
When importing large files we can observe these error messages:
Cause:
Instance has been created in mod-inventory and DI_COMPLETE event sent, after this duplicated event to create instance can be send again to mod-inventory and mod-inventory sends DI_ERROR event with error message that instance already exists to SRM. This DI_ERROR event already has different event id and duplicated record inserted in SRM journal_records table.
To prevent this needed to not not send DI_ERROR from mod-inventory in case when entity already created in inventory-storage.
Notes for devs:
To reproduce it source code in mod-inventory can be modified with invoking CreateInstance/CreateHolding/CreateItem handler twice for testing purposes. Also this can be considered as a scenario for an integration test.
TestRail: Results
Attachments
Issue Links
- blocks
-
MODDICORE-250 Release v3.3.1 (R1 Lotus Bugfix)
-
- Closed
-
-
MODINV-653 Release v18.1.1 (R1 Lotus Bugfix)
-
- Closed
-
- defines
-
UXPROD-3261 NFR: R1 2022 Lotus Data import performance work
-
- Closed
-
- is cloned by
-
MODDICORE-253 Add logic to skip sending DI_ERROR from mod-inventory in case for duplicates - LOTUS Bugfix
-
- Closed
-
-
MODINV-664 Add logic to skip sending DI_ERROR from mod-inventory in case for duplicates - Morning Glory
-
- Closed
-
- relates to
-
MODDICORE-255 Check and fix the sending of DI_ERROR after appears DuplicateEventException - Lotus BF
-
- Closed
-
-
MODDICORE-260 Check and fix the sending of DI_ERROR after appears DuplicateEventException - Morning Glory
-
- Closed
-
-
RMB-899 Extend error handling for a specific status code(4XX) in case of "23505" Postgres error for skipping DI_ERROR from mod-inventory in case for duplicates
-
- Open
-
- mentioned in
-
Page Loading...