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

XML Stream size issue - SFDC integation not possible on upgrade

SA-40835

Summary



In Pega 7.2.2, when the XML stream rule has more elements then at the time of execution of the rule, user gets the below runtime validation error.
Local change recommended in PDN Support Article https://pdn.pega.com/support-articles/connect-soap-stream-rule-compile-error-65535-bytes-limit cannot be applied in the user scenario.

Error Messages



Failed to compile generated Java com.pegarules.generated.xml.ra_stream_pyanyns_pyanyname_98d02ae8a183437ddf2626963f4a4c4e: ----------
1. ERROR in /com/pegarules/generated/xml/ra_stream_pyanyns_pyanyname_98d02ae8a183437ddf2626963f4a4c4e.java (at line 72)
public void execute() {
^^^^^^^^^
The code of method execute() is exceeding the 65535 bytes limit
----------
1 problem (1 error)
Compile failed.


Steps to Reproduce

  1. Migrate the rules from Pega 7.1.7 to Pega 7.2.2.
  2. Regenerate the XML Stream rules by using the new 'Create SOAP Integration' widget.
  3. Run the activity that calls the service.


Root Cause



A necessary change in the settings for the internal Java compiler caused the generation of larger binaries; in this particular case the WSDL was too large leading to the issue.

Resolution



Apply hot fix HFix-34551.
It changes the generated source code that is split into several functions instead of one monolithic method.

Published August 26, 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