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

Production down after major upgrade on Friday

SA-1775

Summary



A migration has been done to Production and since this implementation the users are not able to access their functionalities correctly.

Scenario:
1. A good number (98) of hotfixes have been implemented to Production.
2. New configuration has been implemented in Production as well, changing most of the entry points.
3. After those implementations, impossible for the users to reach their application functionalities.



Error Messages



Lot of errors on the logs - see Root Cause section for example.


Steps to Reproduce



This situation has been replicated internally.


Root Cause



A lot of the following exception were reported on the logs:



 
This type of exception is clearly explained on the following PDN article:
 
https://pdn.pega.com/process/troubleshooting-fail-to-compile-generated-java-for-flows-in-draft-mode-on-production-system




Resolution



Abackup of the Production system has been implemented.
From the configuration side, all the flows in DRAFT mode have to be changed to avoid the compilation exception on Production. A flow in DRAFT mode in Production will not be executed correctly.

XML of the flow looks like that:


.
 
Suggest Edit

Published January 31, 2016 - Updated December 2, 2021

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