File Listener after upgrade from Pega 6.2 to 7.3 is not placing file in the work_listenername directory
Hi,
We have upgraded the Pega application from 6.2 to 7.3 Post upgrade we are noticing that the file listener is behaving in a different way in v7. In v7 after the listener wakes up it is keeping the file in the same path while it is processing and finally moving it to /work_listenername/completed folder. Whereas in v6 the listener after it wakes up deleting the file from the source path, renaming it with a 16 digit number and placing it in the /work_listenername folder.Finally after processing the file is moved to the completed folder. Is there any change to the internal processing logic of File Listener in v7.3 is what we are wondering ? Please respond if anyone faced the same issue in their project.
***Updated by moderator: Lochan to add Categories***
Accepted Solution
Techmahindra
IN
Hello Roy,
Yes the internal code of File listener is changed hence only the behaviour of processing the file at source location. This change is from PRPC 7.2.2 before versions all report as mentioned in V6. Other than this behaviour are you facing any issues in the file processing?
Regards,
Shanthini Charles
Accenture LLP
US
Thanks Shanthini. This explains the behavior we are observing in v7.3. So if the file is getting processed at the source location itself, will the listener that first picks the file for processing hold the lock on the file while it is being processed so that other listeners running on different nodes for a multi-node environment do not process the same file. Could you please share some insight into this as well.
Techmahindra
IN
Hi Roy,
In Listener's Process tab you can have the Lock listener's temporary file checkbox marked
|
Leave this check box cleared in most situations, specifically when a system consists of a single server node or the file listener is set to run on only a single node. |
Hi Roy,
In Listener's Process tab you can have the Lock listener's temporary file checkbox marked
|
Leave this check box cleared in most situations, specifically when a system consists of a single server node or the file listener is set to run on only a single node. Select this check box to cause each listener thread to lock the temporary files that it creates, which helps to avoid name collisions when multiple copies of the listener are running. Select this check box only when required, because locking adds processing that can impact performance. |
Regards,
Shanthini Charles
CTS
US
we had a weird issue , where it processed file and can view data in tables, not sure where the file disappeard. Do not see file anywhere in the entire directory.
Also the timestamp is not added few times, but file is processed and moved to completed folder.