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

Change in max number of pyEmailMaxResends does not reflect

SA-23510

Summary



A change in max number of pyEmailMaxResends (from 3 to 5) and restarting the web server does not change the value. 
 

Error Messages



Not Applicable


Steps to Reproduce



1. Open Pega-ProcessEnginepyEmailMaxResends and change all values to 5 (from 3)
2. Stop and Start web server
3. Stop connection to SMTP server (unplug network cable)
4. Check log for retry (search for ERROR - Data-Corr-Email that failed to send)


Root Cause



A defect or configuration issue in the operating environment. 

pyEmailMaxResends works only for recoverable error. The use case here is of a non-recoverable error and hence, pyEmailMaxResends is not considered.

Resolution



Perform the following local-change:

There are the two errors which are considered as recoverable errors.
 
if(cause.getMessage().toLowerCase().indexOf("connection reset") >= 0) 

recover = 1; 

} if(e.getMessage() != null) 

msg = msg + ": " + e.getMessage(); 
if(msg.toLowerCase().indexOf("could not connect to smtp host") >= 0) 

recover = 1; 


This is in function, pega_integrationengine_default.SendEmailMessage.

As the use case is of non-recoverable error, add the error in function, pega_integrationengine_default.SendEmailMessage.
Suggest Edit

Published May 21, 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