此内容没有您所选择的语言版本。
Chapter 5. Known issues
This section lists known issues with Red Hat Decision Manager 7.3.
5.1. Upgrading
After upgrading to Red Hat Decision Manager 7.3.0, rules do not fire.
Issue: If you upgrade to Red Hat Decision Manager 7.3.0, rules do not fire because of a change to packages in the kmodule.xml file. For more information, see Rules don’t fire after upgrading to RHDM 7.3.0.
5.2. Business Central
All line separators in the right-hand side of rules in the spreadsheet are escaped [RHDM-903]
Issue: If you have multiple lines in the ACTION column of a spreadsheet, all line separators are converted to \n. This conversion causes a build error.
Steps to reproduce:
- Add more than one line to a row in the in ACTION column of a spreadsheet.
- Build the spreadsheet with Red Hat Decision Manager.
Expected result: The spreadsheet builds successfully.
Actual result: The build fails with errors similar to line 1:15 no viable alternative at character '\'.
Workaround: Ensure that rows in the ACTION column of a spreadsheet do not contain more than one line in each row.
You cannot upload a spreadsheet that contains a large decision table [RHDM-488]
Issue: If you try to upload a spreadsheet that contains a large decision table into Business Central, an out-of-memory error appears in the error.log file.
Steps to reproduce:
- Create a spreadsheet that contains a large decision table.
- Create a new project in Business Central.
- Click Add Asset and then select Spreadsheet Decision Table.
- Attach the spreadsheet that contains the large decision table.
-
Review the server
error.logfile.
Actual result: An out-of-memory error appears in the error.log file.
Workaround: None.
An unexpected error occurs if you delete a project that contains a business process [RHPAM-1943]
Issue: If you delete a project that contains a business process, an unexpected error occurs.
Steps to reproduce:
- Create a project in Business Central.
- Add a business process asset to the project.
- Save the business process asset.
- Delete the business process asset.
Expected result: The business process asset is deleted.
Actual result: An error occurs.
Workaround: None.
5.3. Installer
The controller URL is not updated in the standalone.xml file if only Decision Server is installed [RHPAM-1781]
Issue: When you run the Red Hat Decision Manager installer and you specify a URL for the controller, the URL is not updated in the Red Hat JBoss EAP standalone.xml and standalone-full.xml files.
Steps to reproduce:
- Run the Red Hat Decision Manager installer.
- Specify an Red Hat JBoss EAP installation for container.
- Select only Process Server to install.
- Select Advanced Configuration and update controller URL.
- Complete the installation.
-
Open the Red Hat JBoss EAP
standalone.xmlorstandalone-full.xmlfile and find the controller URL.
Expected result: The value of the controller URL property is the URL that you entered during installation.
Actual result: The value of the controller URL property is the default value.
Workaround: Manually update the value of the controller URL property in the Red Hat JBoss EAP standalone.xml and standalone-full.xml file.
5.4. Decision Server
You cannot deploy a KJAR with a PMML asset to a Decision Server Spring Boot starter on Windows [RHDM-852]
Issue: If a KJAR contains a PMML asset, you cannot deploy it as a container on a Decision Server that is running in the kie-server-spring-boot-starter Spring Boot starter on Microsoft Windows.
Steps to reproduce:
- Create a KJAR that contains a PMML asset.
-
Start
kie-server-spring-boot-starteron Windows. -
Deploy the KJAR to a Decision Server that is running the
kie-server-spring-boot-starterSpring Boot starter on Microsoft Windows.
Expected result: The KJAR is deployed successfully.
Actual result: The KJAR cannot be deployed.
Workaround: None.
5.5. OpenShift
User password is displayed in the Readiness and Liveness probes [RHDM-848]
Issue: If you deploy Red Hat Decision Manager on OpenShift, the user password is displayed in both the Readiness and Liveness probes.
Workaround: None.
5.6. Red Hat Business Optimizer
ScoreCalculationCountLimit termination does not work with multi-threaded solving [RHDM-740]
Issue: Red Hat Business Optimizer configured with the score calculation count termination (ScoreCalculationCountLimit) does not terminate. The score calculation count termination is primarily used for testing.
Workaround: Use another type of termination.
