File Listener does not pick the file for processing from Work Folder
File Listener Picks up the file from the Source Location and places it in Work Folder. However the Service File does not pick the file from the work folder and process it and move it to Completed Folder. Please refer the attachments.
***Moderator Edit-Vidyaranjan: Updated Platform Capability***
Accepted Solution
Proximus
BE
Nothing is written in logs during the partial processing?
Are you sure your file listener credentials or the one of service package are working fine?
You should either trace or add debug/log lines in activity which is handling records to get some info.
It's like it starts the work but then it's stuck immediatly. Remove any limitation from your File listener setup (concurrent thread, max requestor, node base). Restart it before any testing.
Check source file for end of line indicator.
Have you got somewhere another FL which is working? (to compare)
If all permissions are fine at server level then it's well the file listener setup
Proximus
BE
Hi,
Have you tried:
- a smaller file
- file with a fully new & never used name (since you've got option Persist Log-Service-File instances)
What's the extension of your file stuck in work dir?
if dup, then it's blocked because of above option.
Regards
Anthony
Farmers insurance
US
Hi Anthony,
- I did try placing a smaller file but no luck.
- I used a new, never used file but no luck. In fact, I selected the option Persist Log-Service-File instances to debug Service-File configuration otherwise it was unchecked all the time.
- The extension of the file that is stuck in work dir is .txt. I did not get when you said if dup, then it is blocked because of the above option.
The history of this File Listener is like it was working when we were in AIX, we recently moved to Linux environment and since then the Listener has stopped working even after the node ID update on the Listener. We are on PEGA 6.3 SP1.
Please let me know if you need any other info. Any kind of help is much appreciated!
Thanks
Goutham
Proximus
BE
Hi,
Hi,
with option Persist Log-Service-File instances, "the system searches the Log-Service-File class for past instances of processing by this listener containing the current file name. If a match is found, the system"
https://collaborate.pega.com/question/file-listener-processing-duplicate-file-names
Have you tried chmod 777 file & all sub dir?
Just to get rid of any permission issue between your user pegatest & owner of dir, inetauto
Anthony
Farmers insurance
US
Hi Anthony,
I have deselected option Persist Log-Service-File instances but the problem still exists. The Source Location /home/pega/exmodCA is already having rwxrwxrwx(Attached a Screenshot). The sub directories, Work & Completed will be created by the File Listener itself so that shows the folder is with 777 permission.
Thanks
Goutham
Proximus
BE
The first dir is well 777 but not work & completed (first doc you sent) which are 775
The file you push in file listener is having 600
Then dir are owned by inetauto and your file owned by pegatest
have you check groups pegatest and checked with inetauto one?
Make a test with everything will full permission and you'll quickly see whether it's your infra or whether it's some pega code issues.
Regards
Anthony
Farmers insurance
US
Antony,
we worked with the unix person and performed the below things.
All the Sub directories were given with rwx access. The file got stuck again in Work folder. We were manually able to place the file in the completed folder showing that the folder has the necessary access. This is making us think that there is some issue in the Service-File. Do you have any other suggestion for us to check on the Service File.
Thanks
Goutham
Accepted Solution
Proximus
BE
Nothing is written in logs during the partial processing?
Are you sure your file listener credentials or the one of service package are working fine?
You should either trace or add debug/log lines in activity which is handling records to get some info.
It's like it starts the work but then it's stuck immediatly. Remove any limitation from your File listener setup (concurrent thread, max requestor, node base). Restart it before any testing.
Check source file for end of line indicator.
Have you got somewhere another FL which is working? (to compare)
If all permissions are fine at server level then it's well the file listener setup
Farmers insurance
US
Hi Antony,
We had put some logs in Service File Activity and nothing was logged.
We have an environment in AIX where the File Listener is working fine so we did a working session with the Infrastructure Unix developer and requested to delete the Source Location created in Linux server and clone the Source Location similar to AIX server. After the server was recycled, the File Listener picked up the new file and processed it. Thank you very much for your assistance!!!
Thanks
Goutham