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

"Queue Full" error attempting to start Facebook connector

SA-39680

Summary



User is observing an outage causing multiple Social Media connectors to fail.

Connectors have been restarted successfully, with posts and tweets being harvested correctly, with the exception of one.

When attempting to restart from the Dataflow landing page in the Designer Studio, the status moves to 'Pending Activation' and then after about 20 seconds moves to Completed.



Error Messages

No errors have been observed, either in in the Dataflow landing page, in the rule form, or using the tracer.
However, the PegaRULES Application log file reports the following:


poll.AbstractPollingConnecter) ERROR <Environment Details Redacted> - Queue full

Steps to Reproduce

  1. Login to the production environment
  2. Navigate to the Dataset rule in Data-Social-Facebook.
  3. Go to Actions > Run and select operation as browse.
  4. Search for 5 records in a window of 2 minutes.
  5. After approximately 20 seconds the results page will flash up with no records.

Root Cause



A defect in Pegasystems’ code or rules


On investigating where the issue is commencing, it appears to be at the Dataset level.

Opening the Dataset and running it directly from the ruleform returns no records.

Root cause is an internal buffer limit (fixed size) of 1,000 messages on the Facebook Connector functionality.
When there are more than 1,000 messages/posts to be processed, the buffer is filled and processing terminates with a "Queue Full" error message.

Resolution



Apply HFix-35150.

Published August 18, 2017 - Updated 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