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

Listener is inconsistent



User has configured an email listener and is frequently unable to connect to it.

All the emails to be processed are adding up to error count until restart. Once restarted, it picks up same records and processes them.

Error Messages

Error in logfile:

javax.mail.MessagingException: Connection timed out;
  nested exception is: Connection timed out
    at com.sun.mail.imap.IMAPStore.protocolConnect(
    at javax.mail.Service.connect(
Caused by: Connection timed out
    at Method)
    at com.sun.mail.util.SocketFetcher.createSocket(
    at com.sun.mail.util.SocketFetcher.getSocket(
    at com.sun.mail.iap.Protocol.<init>(
    at com.sun.mail.imap.protocol.IMAPProtocol.<init>(
    at com.sun.mail.imap.IMAPStore.protocolConnect(

Steps to Reproduce

Not Applicable.

Root Cause

As there are frequent exceptions in the log file, after each exception latency of email listener is being increased based on a pre-defined logic, irrespective of what has been defined on the email listener rule form.


Few DSS settings were applied, which were supposed to reduce the latency.

DSS: email/exceptionLatency and DSS: email/initialLatencyTime.

As user's issue persisted which is, sleep time was increasing, causing more latency post exception, the issue is resolved through
HFix-24902 . 

Suggest Edit

Published May 4, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

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