Skip to main content

Troubleshooting FUA Compiler Error “Requires a 1.6 compliant JVM”


Different components of the system fail because of errors in Rule Assembly (First-Use Assembly, FUA) displayed in the Pega logs and other exceptions. This problem has been reported for Pega Platform deployments running on Java version 11.

Here are a couple of example scenarios for which the problem was reported:

SYSTEM-QUEUE-SCHEDULEDTASK that sends email fails daily.

After updating your Pega on-premises deployment from Pega 8.5.1 to 8.5.3, you observe that the Static Assembler shows 36 rules failing with the error that generated Java code requires a 1.6 compliant JVM.


Caused by: Failed to compile generated Java com.pegarules.generated.activity.ra_action_createcommonlogger_60cfa081bdece6891ff9a834e9abea64: Annotation processing got disabled, since it requires a 1.6 compliant JVM


To identify if an incident is related to this problem, locate the following line in the Pega log file along with other Rule Assembly failure exception messages:

Annotation processing got disabled, since it requires a 1.6 compliant JVM


To resolve the problem, perform the following local change:

  1. Restart all nodes.
  2. After the restart, check to see if the problem still exists. If the problem does not go away, proceed to the next step.
  3. Shut down all the nodes.
  4. Back up the database table: pr_assembled_classes
  • Oracle DB: Use SQL Developer to export the data as DML queries for the table PEGA_RULES.pr_assembledclasses.
  • PostgreSQL: Use the command pg_dump -U <database-username> -d <database-name> -t pr_assembledclasses > /opt/assembled_classes.dump
  • Microsoft SQL Server: Use the SQL Server Import and Export Wizard for exporting the table PEGA_RULES.pr_assembledclasses as a Microsoft Excel file.
  1. Truncate the table PEGA_RULES>.pr_assembled_classes.

    truncate table PEGA_RULES.pr_assembledclasses;
  1. Start one Web node. Check to see if the problem persists.
    • If the problem is resolved, send the incident details along with the logs and the table backup from the Step 4 in a new Incident (INC) that you create in My Support Portal. (See Step 9.)
    • If the problem persists, proceed to the next step.
  2. Stop the running node.
  3. Truncate the following tables:

-- Application-Based-Assembly (ABA) Cache ---

truncate table PEGA_RULES.pr_sys_appcache_dep;

truncate table PEGA_RULES.pr_sys_appcache_entry;

truncate table PEGA_RULES.pr_sys_appcache_shortcut;


-- Virtual Table (V-Table) Cache--

truncate table PEGA_RULES.pr_sys_rule_impl;

-- Additional - System-CachedConclusion ----

truncate table PEGA_RULES.pr4_rule_sysgen;

truncate table PEGA_RULES.pr_assembledclasses;

-- The most recent pulse processing by the Pega database agent---


-- Static Content----

truncate table PEGA_RULES.pr_sysgen_static_content;

-- Status node entries

truncate table PEGA_DATA.PR_Sys_StatusNodes;

truncate table PEGA_DATA.PR_Sys_StatusDetails;

  1. Go back to Step 6 and check to see if the problem persists:
    • If everything works as expected on one node, start the other nodes.
    • If the problem persists, submit an INC:
      1. Go to My Support Portal.
      2. For New Request, click For an issue I’m having.
      3. Complete all fields of the form and Submit it.
Severity 1 Incidents (production system is down) require you to call your Pega Support regional office.
Did you find this content helpful?

100% found this useful

Related Content

Have a question? Get answers now.

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

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

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