Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

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.

Issue: Java 64K Method Size Limit

Updated on September 13, 2021

Symptom

If you save a rule form or compile a rule (when it is first assembled for execution), the generated code may exceed the the Java and JSP 64K size limit.

An error similar to the following occurs:

Failed to compile generated Java
com.pegarules.generated.flowaction.ra_flowaction_bbt_olb_onlineac
countopening_newapplication_returntocip_inputenabled_82850f36ea01
1e06f181051d0fcab429: ---------- 1. ERROR in
/tmp/PegaRULES/temp/PRGenJava/com/pegarules/generated/flowaction/
ra_flowaction_bbt_olb_onlineaccountopening_newapplication_returnto
cip_inputenabled_82850f36ea011e06f181051d0fcab429.java (at line
292) public void _jspService(HttpServletRequest request,
HttpServletResponse response) throws java.io.IOException,
ServletException { ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
The code of method _jspService(javax.servlet.http.HttpServletRequest,
javax.servlet.http.HttpServletResponse) is exceeding the 65535
bytes limit ---------- 1 problem (1 error)

NOTE: This sample error displayed when a flow action rule exceeded the 64K limit. Errors you encounter may differ depending on where in your system the limit is exceeded.

Solution

Workaround

This message describes a Java compiler constraint. You must simplify the rule causing this error so that the resulting Java method size is 64KB or less.

Tags

Pega Platform 7.1.1 - 8.3.1 System Architect System/Cloud Ops Administrator System Administration

Have a question? Get answers now.

Visit the Support 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.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us