Support Article
Error in the PR_LOG table: Infinite loop detected in Svc File
SA-84269
Summary
Error occurs when the file listener has an empty file.
Error Messages
File listener failed with error -- Error in the PR_LOG table: Infinite loop detected in service File; nothing read from structured parse rule.
00000079 SystemOut O [FILE-Thread-2312] [STANDARD] [ ] [ ] (services.file.FileActionImpl) ERROR File.alistener|ATRUCY8L95ESAMC1VB5SVC9VJE7C7X6AZ|-1649640902.1559447220637000 - Caught throwable processing your_file.pst
com.pega.pegarules.pub.PRRuntimeException: Infinite loop detected in service File; nothing read from structured parse rule [your_ParseRule].
at com.pega.pegarules.integration.engine.internal.services.file.RuleServiceFile.parseByRecordType(RuleServiceFile.java:1332) ~[printegrint.jar:?]
at com.pega.pegarules.integration.engine.internal.services.file.RuleServiceFile.process(RuleServiceFile.java:1769) ~[printegrint.jar:?]
at com.pega.pegarules.integration.engine.internal.services.file.FileActionImpl.execute(FileActionImpl.java:443) ~[printegrint.jar:?]
at com.pega.pegarules.storage.DirectoryPollingWatcher.run(DirectoryPollingWatcher.java:83) ~[prprivcommon.jar:?]
at com.pega.pegarules.integration.engine.internal.services.file.FileListener.run_(FileListener.java:468) ~[printegrint.jar:?]
at com.pega.pegarules.integration.engine.internal.services.listener.ServiceListenerBaseImpl.run(ServiceListenerBaseImpl.java:454) ~[printegrint.jar:?]
at java.lang.Thread.run(Thread.java:811) [?:2.9 (02-08-2018)]
Steps to Reproduce
Configure a file listener with an empty file.
Root Cause
A defect in Pegasystems’ code or rules.
Issue in the order in which the activities occur or in the behavior of a non-local file system (NetApp appliance).
When processing, the listener obtained a lock on the file name using syslocks.
- The listener processes the file.
- The listener renames the file to the completed folder.
- The listener releases the lock.
The second thread on a different node obtained the lock and attempted to process. At that time, the file system is in sync and the file is missing in mid parse. This caused the parse rule to fail with an Infinite loop detected in the Service File.
Below is the data supporting the theory:
In the above error, the file name is your_file.pst. and occurs at about 20:47 on 6/1.
The following table displays the below nodes processing the your_file.pst at that time.
- 1d8119eff845cf041b34a84fc037f263
- 46da9a7cb27a3ed61f6c70ec76a9968c
| FILE_ID | FILE_NAME | FOLDER | CREATE_TIMESTAMP | TYPE | FILE_TYPE | SYSTEM | ERROR_TYPE | ERRO_DESC | REPORTED | NODE_ID |
| F-79268 | your_fil.pst | //NFS/Inbound | 01-JUN-19 20:47:00 | IN | POSTBACK | your_system | 0 | 1d8119eff845cf041b34a84fc037f263 | ||
| F-79269 | you_file.pst | //NFS/Inbound | 01-JUN-19 20:47:00 | IN | POSTBACK | your_system | 1 | DUPLICATE | 1 | 46da9a7cb27a3ed61f6c70ec76a9968c |
Resolution
Here’s the explanation for the reported behavior:
The file is moved out from the Parse rule after the details of the file system are propagated to each node.
Published October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.