Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Error in the PR_LOG table: Infinite loop detected in Svc File



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 Infinite loop detected in service File; nothing read from structured parse rule [your_ParseRule]. 
at ~[printegrint.jar:?] 
at ~[printegrint.jar:?] 
at ~[printegrint.jar:?] 
at ~[prprivcommon.jar:?] 
at ~[printegrint.jar:?] 
at ~[printegrint.jar:?] 
at [?: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.
  1. The listener processes the file.
  2. The listener renames the file to the completed folder.
  3. The listener releases the lock.
If the file system is a network appliance, it is conceivable for the release of the lock to happen, and another instance of the listener to obtain the lock and attempt to process the file. The parser in this case, is a duplicate entry that is logged in the pr_log file.

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.
  1. 1d8119eff845cf041b34a84fc037f263
  2. 46da9a7cb27a3ed61f6c70ec76a9968c
Eventually, 46da9a7cb27a3ed61f6c70ec76a9968c reported it as a duplicate. This is the same node that generated the error due to the Hazelcast node table entry earlier in the log file.
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


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

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us