EDI: fetcher repeatedly downloads and processes problematic message files
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
Medium
|
Unassigned | ||
2.10 |
Fix Released
|
Undecided
|
Unassigned | ||
2.11 |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
The EDI fetcher process compares the names of incoming files against files that have already been downloaded and stored in acq.edi_message by checking host, username, password, directory, file name... AND whether the acq.edi_message row has a status of 'processed'.
This means that if a given message can never be successfully processed for whatever reason, and if the materials vendor never deletes the file from their server, each run of edi_fetcher.pl will cause the same problematic file to be retrieved and (unsuccessfully) processed, thereby causing acq.edi_message to continue to grow. In the wild, this has resulted in a situation where one database had over 15,000,000 useless rows in acq.edi_message.
Evergreen master
tags: | added: acq edi |
Changed in evergreen: | |
importance: | Undecided → Medium |
Changed in evergreen: | |
milestone: | none → 2.12-beta |
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
A patch is available in the user/gmcharlt/ lp1662902_ edi_fetcher branch of the working/Evergreen repository:
http:// git.evergreen- ils.org/ ?p=working/ Evergreen. git;a=shortlog; h=refs/ heads/user/ gmcharlt/ lp1662902_ edi_fetcher