Red Hat Training

A Red Hat training course is available for Red Hat Process Automation Manager

Chapter 4. Known issues

This section lists known issues with Red Hat Process Automation Manager 7.2.

4.1. Installer

When installing Process Server and Business Central using the Red Hat Process Automation Manager installer, the default placeholder for the controller URL should contain business-central [RHPAM-1774]

Issue: If you use the Red Hat Process Automation Manager installer to install both Business Central and Process Server, on the Advanced Configuration page the default value for Process Server is incorrect.

Steps to reproduce:

  1. Use the installer to install Red Hat Process Automation Manager on Red Hat JBoss EAP.
  2. Accept all default selections.
  3. On the Advanced Configuration page, select Configure Process Server.

Expected result: The value of the Process Server URL is http://localhost:8080/business-central/rest/controller.

Actual result: The value of the Process 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/business-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 Process Server is installed [RHPAM-1781]

Issue: When you run the Red Hat Process Automation 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:

  1. Run the Red Hat Process Automation Manager installer.
  2. Specify an Red Hat JBoss EAP installation for container.
  3. Select only Process Server to install.
  4. Select Advanced Configuration and update controller URL.
  5. Complete the installation.
  6. Open the Red Hat JBoss EAP standalone.xml or standalone-full.xml file 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. Business Central

Red Hat Decision Central 7.0 and earlier and BRMS 6.4 and earlier repositories are not fully migrated when imported into Business 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 Business 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:

  1. In Red Hat Process Automation Manager 7.0.0 or earlier, create a repository with two projects.
  2. Copy the repository location from the .niogit directory.
  3. Open Red Hat Process Automation Manager 7.2.0.
  4. Click LibraryImport Project.
  5. 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 Process Automation Manager 7.2.

A TimeoutException error occurs when logging in to a clustered Business Central [RHPAM-1749]

Issue: On a clustered Business Central instance, when logging in to Business Central an exception is thrown.

Steps to reproduce:

  1. Create a Business Central cluster configuration that uses ElasticSearch and AMQ Broker, and that has two standalone Business Central nodes.
  2. Uncomment the <distributable/> tag on both Business Central nodes.
  3. Log in to Business 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 Process Automation Manager integrated with Red Hat Single Sign-On ignores user SSH key when working with Git [RHPAM-1683]

Issue: With Red Hat Process Automation 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:

  1. Integrate a Red Hat Process Automation Manager installation with Red Hat Single Sign-On, as described in Integrating Red Hat Process Automation Manager with Red Hat Single Sign-On.
  2. Use the Red Hat Process Automation Manager AdminSSH Keys page to add a public SSH key.
  3. 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>
  4. 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 Business Central Data Sources perspective [RHPAM-1741]

Issue: When you access the Business 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:

  1. Log in to Business Central with the admin role.
  2. Go to AdminDatasources.

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 Business Central and go to AdminDatasources. These errors only appear the first time you click the perspective after installation.

4.3. Process 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:

  1. Create a project with a process.
  2. Deploy the project and start the process.
  3. Go to MenuDeployExecution Servers and stop the container.

Actual result: The container is removed from the UI even though it is still running.

4.4. Maven repository

Missing JWS dependencies in the offline Maven repositories distribution [RHPAM-1715]

Issue: The following key dependencies required to install Process Server on Red Hat JBoss Web Server are missing from the offline Maven repository.

org.jboss.integration:narayana-tomcat
org.jboss:jboss-transaction-spi

If you are performing a manual installation, you must copy the files described in the workaround.

Workaround:

  1. Use the installer to install Red Hat Process Automation Manager on Red Hat JBoss Web Server.
  2. In a terminal, change directory to the <JWS-HOME>/jws-5.0/tomcat/lib directory where the installer installed Red Hat Process Automation Manager.
  3. Copy the following files from the <JWS-HOME>/jws-5.0/tomcat/lib directory to the <JWS-HOME>/jws-5.0/tomcat/lib directory of the target Red Hat JBoss Web Server location.

    narayana-tomcat-1.0.0.Final-redhat-1.jar
    jboss-transaction-spi-7.6.0.Final-redhat-1.jar

4.5. OpenShift

Various errors occur when starting clustered Business Central on OpenShift [RHPAM-1747]

Issue: When clustered Business Central is started on OpenShift using the rhpam72-authoring-ha.yaml template, Business Central sometimes throws various exceptions that cause the pod to restart or the deployment to fail.

Steps to reproduce:

  1. Use the rhpam72-authoring-ha.yaml template to deploy Red Hat Process Automation Manager 7.2 images on OpenShift.
  2. Check the Business 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.

4.6. Process designer

In the new process designer, when a process containing another event subprocess is created and saved, the process validation fails [RHPAM-1732]

Issue: In the new process designer, when a subprocess containing another event subprocess is created and saved, the process validation fails.

Note

As a result of this issue, you cannot add an event subprocess into another (embedded) subprocess in the new process designer.

Steps to reproduce:

  1. Create a process with at least one subprocess.
  2. Click Save.

Expected result: The process and subprocesses are saved.

Actual result: The following validation error appears even though all sequence flows have their source and target within the process:

Sequence flow connectors cannot exceed the embbedded subprocess' bounds. Both source and target nodes must be in same parent process.