Discussion
filelistener failing in multinode system very frequently
Hi,
Can anyone help me here to resovling the issue of file listener. It gets down the very next moment we start it. But this is happening only for few file listener only, where we have parent folder and child folder.
Error in logs says {folder name} does not exist
and sometime is say {folder name} exist , but not a valid directory.
Shared folders have read and write access both.
Please let me know if anyone has encountered these issues and how to get rid of this.
Thanks
Akshay !
Test connectivity is always successful, listener is having access to it, but we have to restart it manually very often. I cannot paste the logs , since it is present in production servers.
We have checked all the prerequisites measure which needs to be checked for file listeners. This issue is happening only for the folders where there are many sub folders inside the folder.All the listener which are configured like this are having problem.
We dnt have any issues with the listeners which are listening from one folder (no child folders).
I have source location given as below in file listener.
D:\PDFTEST\Test71
PDFTEST -> Parent Folder
Test71 -> child folder
I was able to connect to it successfully. Can you please provide the folder structure or correct me if I am wrong.
It is correct only. Similary if there are other child folders say Test72, Test73.. etc, all the listener which are poniting to this child folder are having this issue
I have created child folder under parent one as below.
D:\PDFTEST\Test71\Test72\Test73\Test74
If I place file in Test74 folder it is being processed and placed in completed folder inside Test74 folder. Might be permission issue or can you check any spaces present in folder names.
Did the listener have access to child folder? Test Connectivity on file listener succeeds or not?
Can you paste the sample stack trace in this thread?