Chapter 4. Known issues
This section lists known issues with Red Hat Decision Manager 7.2.
4.1. Installer
When installing Decision Server and Decision Central using the Red Hat Decision Manager installer, the default placeholder for the controller URL should contain decision-central [RHPAM-1774]
Issue: If you use the Red Hat Decision Manager installer to install both Decision Central and Decision Server, on the Advanced Configuration page the default value for Decision Server is incorrect.
Steps to reproduce:
- Use the installer to install Red Hat Decision Manager on Red Hat JBoss EAP.
- Accept all default selections.
- On the Advanced Configuration page, select Configure Process Server.
Expected result: The value of the Decision Server URL is http://localhost:8080/decision-central/rest/controller.
Actual result: The value of the Decision Server URL is http://localhost:8080/controller/rest/controller.
Workaround: After you complete the installation, change http://localhost:8080/controller/rest/controller to http://localhost:8080/decision-central/rest/controller in the the Red Hat JBoss EAP standalone.xml and standalone-full.xml files.
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.
4.2. Decision Central
Red Hat Decision Central 7.0 and earlier and BRMS 6.4 and earlier repositories are not fully migrated when imported into Decision Central [RHPAM-1768]
Issue: Red Hat Decision Central 7.0 and earlier and BRMS 6.4 and earlier repositories (legacy structure repositories) that contain more than one project can be imported into Decision Central even though they are not supported. When these repositories are imported, the are not fully migrated and will not perform as expected.
Steps to reproduce:
- In Red Hat Decision Manager 7.0.0 or earlier, create a repository with two projects.
-
Copy the repository location from the
.niogitdirectory. - Open Red Hat Decision Manager 7.2.0.
-
Click Library
Import Project. - Paste the repository location and select both projects.
Actual result: The projects are imported but will not perform as expected.
Workaround: Use the patching and upgrading tool to import Red Hat Decision Central 7.0 and earlier and BRMS 6.4 and earlier repositories, as described in Patching and upgrading Red Hat Decision Manager 7.2.
A TimeoutException error occurs when logging in to a clustered Decision Central [RHPAM-1749]
Issue: On a clustered Decision Central instance, when logging in to Decision Central an exception is thrown.
Steps to reproduce:
- Create a Decision Central cluster configuration that uses ElasticSearch and AMQ Broker, and that has two standalone Decision Central nodes.
-
Uncomment the
<distributable/>tag on both Decision Central nodes. - Log in to Decision Central on one of the nodes.
Actual result: An exception is thrown.
Workaround: See the workaround in the JBoss EAP 7 does not process requests for a session in parallel article.
Red Hat Decision Manager integrated with Red Hat Single Sign-On ignores user SSH key when working with Git [RHPAM-1683]
Issue: With Red Hat Decision Manager integrated with Red Hat Single Sign-On, if you try to clone a project created by a user that has an SSH key set, you cannot clone it without the SSH key password. The SSH key is ignored.
Steps to reproduce:
- Integrate a Red Hat Decision Manager installation with Red Hat Single Sign-On, as described in Integrating Red Hat Decision Manager with Red Hat Single Sign-On.
-
Use the Red Hat Decision Manager Admin
SSH Keys page to add a public SSH key. Enter the following command in a terminal to add a private SSH key to your
ssh-agent, where<SSH-KEY-PATH>is the path to the SSH private key:$ ssh-add <SSH-KEY-PATH>
Use SSH to clone the project, for example:
git clone ssh://user@localhost:8001/space/project
Expected result: The project is cloned.
Actual result: You cannot clone the project unless you use the user’s password.
Several Errai projects contain XSD-invalid pom.xml file [RHPAM-1742]
Issue: Maven repository validation identified the following pom.xml files in the Errai project, which are invalid according to Maven POM XSD:
org/jboss/errai/errai-ioc/4.4.1.Final-redhat-00001/errai-ioc-4.4.1.Final-redhat-00001.pom.xml org/jboss/errai/errai-navigation/4.4.1.Final-redhat-00001/errai-navigation-4.4.1.Final-redhat-00001.pom.xml org/jboss/errai/errai-security-server/4.4.1.Final-redhat-00001/errai-security-server-4.4.1.Final-redhat-00001.pom.xml org/jboss/errai/errai-security-client/4.4.1.Final-redhat-00001/errai-security-client-4.4.1.Final-redhat-00001.pom.xml org/jboss/errai/errai-common/4.4.1.Final-redhat-00001/errai-common-4.4.1.Final-redhat-00001.pom
Workaround: None.
kie-soup-dataset-elasticsearch is an XSD-invalid pom.xml file [RHPAM-1743]
Issue: Maven repository validation identified the kie-soup-dataset-elasticsearch pom.xml fileas invalid according to Maven POM XSD.
Workaround: None.
Two ClassNotFoundExceptions errors are thrown the first time you open the Decision Central Data Sources perspective [RHPAM-1741]
Issue: When you access the Decision Central Data Sources perspective for the first time after a clean installation, the following ClassNotFoundExceptions errors appear in the server.log file:
org.guvnor.structure.repositories.NewBranchEvent org.guvnor.structure.repositories.RepositoryUpdatedEvent
Steps to reproduce:
-
Log in to Decision Central with the
adminrole. -
Go to Admin
Datasources.
Actual result: As soon as you click the Data Sources perspective, two errors appear in Red Hat JBoss EAP console.
Expected result: No errors appear.
Workaround: Restart Decision Central and go to Admin
4.3. Decision Server
A container is removed from the UI even though it was not possible to stop it [RHPAM-1698]
Issue: A container cannot be stopped if it is blocked by an active process instance. However if you attempt to stop a blocked container from the UI, the action throws an exception and the container disappears.
Steps to reproduce:
- Create a project with a process.
- Deploy the project and start the process.
-
Go to Menu
Deploy Execution Servers and stop the container.
Actual result: The container is removed from the UI even though it is still running.
4.4. OpenShift
Various errors occur when starting clustered Decision Central on OpenShift [RHPAM-1747]
Issue: When clustered Decision Central is started on OpenShift using the rhpam72-authoring-ha.yaml template, Decision Central sometimes throws various exceptions that cause the pod to restart or the deployment to fail.
Steps to reproduce:
-
Use the
rhpam72-authoring-ha.yamltemplate to deploy Red Hat Decision Manager 7.2 images on OpenShift. - Check the Decision Central log files.
Expected result: No errors appear in the log files.
Actual result: Errors appear in the log files, the pod restarts, or the deployment fails.
Workaround: None.
