File Listener incorrectly marks files as Duplicate
User has independent file listeners, one for each application deployed on the instance.
Each listener has it's own directory that it listens on. Each listener has it's own service package and therefore file service defined and “Ignore duplicate file names?" is enabled.
A file of the same name is delivered to both listener directories.
Whichever listener picks up the file works as expected, the other listener picks up the file but immediately marks it as a duplicate.
This is unexpected given the listeners are different file services with unique listening directories.
No error message, but the second file is just marked as a duplicate.
Steps to Reproduce
- Create two file services, two file listeners listening to two different directories with “Ignore duplicate file names?" enabled.
- Deliver a file of the same name to both and see that second listener marks the file as a duplicate.
This behavior is consistent in all the versions (up to 7.2.2) and the system will check the Log-Service-File instances based on FileName as sole criteria to determine the duplicity of a particular file input.
So, even though two different listeners (sourcing from two different directories) has encountered files with the same name, the latter processing one will end up as a duplicate file.
ResolutionIn order to avoid duplicate file name, ensure that unique file names are used when inputting files to the listener directories.
In addition to this the following have been raised:
1) A request for a Pega Help File update to clarify that the duplicate checking from 'Ignore duplicate file names' will be across ALL listeners once the file name has been processed by one listener.
2) An enhancement request, FDBK-18629 “Update 'Ignore duplicate file names' to occur per File Listener”, has been created for consideration by Pega Product Management.