• File listeners fail to start
• File listeners fail to start after a system restart
• File listener cannot find the files to process
• Empty files are not processed
• File listener fails to authenticate
• File listener throughput is slow
• Partially processed files are not finished after a node goes down
• File listener does not process a file

File listeners fail to start

This problem might be indicated by "Time out borrowing service requestor" or "Unable to create listener" messages in the log file.

• If you are seeing time-out exceptions regarding the requestor pool, consider increasing the requestor pool size on the Pooling tab of the service package data instance.
• Ensure that the source location path is configured correctly on the Properties tab of the file listener. You can view configured storage destinations on the File Storage landing page. For more information, see Viewing file storage destinations.
• Ensure that the Service access group configured in the service package has access to the service rules and service activities to be used by the requestor.

File listeners fail to start after a system restart

Ensure that your startup options are configured correctly. For more information, see Where, when, and whether file listeners start.

File listener cannot find the files to process

This problem might be indicated by a "no such file or directory" message in the log file.

• For cloud environments, ensure that you are using either the Pega Cloud Storage repository or another repository type that is supported on cloud, and not the local file system for processing files. For more information, see Adding a file repository.
• For on-premises environments, ensure that the folder used for processing has file permissions set to 777.
• If files are not processing, or files are moved to completed without processing, consider changing the polling interval to be greater than the expected file processing time. For more information, see Configuring file listener processing and Best practices for processing files using the file listener.
• Ensure that you are correctly filtering the files to process. For more information, see Creating a file listener.

Empty files are not processed

Ensure that the Process empty files option is selected. For more information, see Configuring file listener processing.

File listener fails to authenticate

This problem might be indicated by "authentication failed for listener" or "authorization failed" messages in the log file. Ensure that the requestor credentials are correct.

File listener throughput is slow

This problem might be indicated by an "authorization failed" message in the log file.

• Ensure that the number of concurrent threads is 1 or a small integer. Each thread operates on a single file, so multithreading has no benefit unless multiple files are available at the same time for processing. If the node on which the file listener runs has available JVM memory and CPU cycles, and multiple files are available for processing, using 2 to 5 threads can increase throughput.
• Ensure that the database is large enough to load data.

Partially processed files are not finished after a node goes down

Ensure that you are using record at a time processing. For more information, see Best practices for processing files using the file listener.

File listener does not process a file

This problem might be indicated by an "unable to find match for record type" message in the log file.

• Check that the file formatting and encoding is correct.
• Ensure that a byte order mark (BOM) is not included at the beginning of the file.