GeneratedCodeMismatchException is thrown when calling soap connector
Hi all,
After analysing performance issues of one of our applications, we found below exception occurring regularly. It did not come up in any of the pega logs, but it did turn up in Dynatrace.
As can be seen in the image, execution time is increase by more than 1,5 minutes by this exception.
Exception:
com.pega.platform.codegeneration.il.GeneratedCodeMismatchException
Message:
IL: com.pega.pegarules.priv.FUAUtil.createQueryBuilder().scalarProperty("pySettingValue").buildPropertyQuery().resolve(tools, pega.findDataPage("D_pxGetApplicationSettingValue", false, "OwningRuleset", "ApplicationX", "Purpose", "Connector..."
Unfortunately the Message was cutoff at the end, making it unclear which Application Setting is referenced. Luckily there are only three application settings used in the configuration of this SOAP connector, which narrows it down considerably.
Hi all,
After analysing performance issues of one of our applications, we found below exception occurring regularly. It did not come up in any of the pega logs, but it did turn up in Dynatrace.
As can be seen in the image, execution time is increase by more than 1,5 minutes by this exception.
Exception:
com.pega.platform.codegeneration.il.GeneratedCodeMismatchException
Message:
IL: com.pega.pegarules.priv.FUAUtil.createQueryBuilder().scalarProperty("pySettingValue").buildPropertyQuery().resolve(tools, pega.findDataPage("D_pxGetApplicationSettingValue", false, "OwningRuleset", "ApplicationX", "Purpose", "Connector..."
Unfortunately the Message was cutoff at the end, making it unclear which Application Setting is referenced. Luckily there are only three application settings used in the configuration of this SOAP connector, which narrows it down considerably.
Running D_pxGetApplicationSettingValue was succesful for all three of these Application Settings. No errors came up in the Tracer, nor were there any exceptions thrown or logged to the Pega logs.
How can we resolve this exception or debug it further?
Pegasystems Inc.
GB
The GeneratedCodeMismatchException typically occurs when there is a mismatch between the generated code and the expected code. This can happen due to various reasons such as changes in the rules, schema changes, or even due to cache issues. To debug this further, you can try the following steps:
- Clear the system cache: Sometimes, the issue can be resolved by clearing the system cache as it might contain stale or corrupted data.
- Trace the connector: Use the Tracer tool to trace the execution of the connector and see if you can identify any issues.
- Check the rules: Verify if there have been any recent changes to the rules that might be causing this issue.
- Check the schema: If there have been any recent changes to the database schema, it might be causing this issue.
If the issue persists, it would be best to contact Pega Support for further assistance. Please provide the INC ticket here so we can help track it.
⚠ This is a GenAI-powered tool. All generated answers require validation against the provided references.
Pega Platform 8.4 Resolved Issues
Pega 8.7.1 - There was a problem getting a list: code: 0 SQLState: HY008
The GeneratedCodeMismatchException typically occurs when there is a mismatch between the generated code and the expected code. This can happen due to various reasons such as changes in the rules, schema changes, or even due to cache issues. To debug this further, you can try the following steps:
- Clear the system cache: Sometimes, the issue can be resolved by clearing the system cache as it might contain stale or corrupted data.
- Trace the connector: Use the Tracer tool to trace the execution of the connector and see if you can identify any issues.
- Check the rules: Verify if there have been any recent changes to the rules that might be causing this issue.
- Check the schema: If there have been any recent changes to the database schema, it might be causing this issue.
If the issue persists, it would be best to contact Pega Support for further assistance. Please provide the INC ticket here so we can help track it.
⚠ This is a GenAI-powered tool. All generated answers require validation against the provided references.
Pega Platform 8.4 Resolved Issues
Pega 8.7.1 - There was a problem getting a list: code: 0 SQLState: HY008
Troubleshooting BIX for on-premises environments > Query timeout exception