Red Hat Summit 红帽全球峰会支持控制台（Console）开发人员开始试用联系人

此内容没有您所选择的语言版本。

Chapter 5. Known issues

This section lists known issues with Red Hat Decision Manager 7.5.

5.1. Business Central
复制链接

You cannot start a task if the Elytron adapter is installed [RHPAM-2450]

Issue: If Business Central on Red Hat JBoss EAP is integrated with RH-SSO using the Elytron adapter, errors are displayed after a task is started.

Steps to reproduce:

  1. Install Red Hat Decision Manager on Red Hat JBoss EAP.
  2. Configure Business Central with RH-SSO using the Elytron adapter.
  3. Import a process sample.
  4. Start the process.
  5. Start a task.

Expected result: The task starts correctly.

Actual result: The task does not start and an error is displayed.

Workaround: Use the legacy adapter instead of the Elytron adapter. Enter the following command to install the legacy adapter: 

./bin/jboss-cli.sh -c --file=bin/adapter-install.cli
Copy to Clipboard Toggle word wrap

An error might occur if you import a sample project twice [RHPAM-2434]

Issue: An Unable to complete your request error might appear if you import a sample project that has already been imported.

Steps to reproduce:

  • Import a sample project twice. Note that this error does not always occur.

Workaround: If the sample project that failed to import is present in your space, remove it then import it again.

In the DMN designer, the DMN file validation operation does not report invalid operators [RHDM-1119]

Issue: In the DMN designer, if the DMN model contains an invalid operator (an operator that does not exist), for example >>>>, the validation operation does not report the invalid operator.

Workaround: None.

Users cannot test DMN context expression in test scenarios [RHDM-1116]

Issue: If you test DMN context expressions using the test scenario designer and the test fails, the corrected output has the wrong format.

Steps to reproduce:

  • Create two tests where the second test is created according to the hint message in the first test, while retaining the same input as the first test.

Expected result: The corrected output has the correct format, as shown in the following example:

{"key_a" : "value_a", "key_b" : "value_b", …​}

Actual result: The corrected output has an incorrect format (missing double quotes), as shown in the following example:

{key_a : value_a, key_b : value_b, …​}

5.2. Decision engine
复制链接

The executable model does not fully parse multi-line patterns [RHDM-1098]

Issue: When a pattern has multiple lines, the executable model does not fully parse its conditions. Only the first line is parsed.

Note

This issue is resolved with Red Hat Decision Manager patch release 7.5.1.

Workaround: None.

5.3. High availability
复制链接

In a high-availability authoring environment, when one user imports a project, another user is unable to see it [RHPAM-2470]

Issue: When multiple users connect to a high-availability Business Central and one user creates a project, another user cannot see the project.

Steps to reproduce:

  1. Log in to Business Central as two different users (A and B) from two different hosts or browsers.
  2. As user A and as user B, open the same space.
  3. As user A, import a project using an external Git repository URL.

Expected result: As user B, you can see the imported project in the space.

Actual result: As user B, you cannot see the imported project in the space.

Workaround: As user B, reload the space.

In a high-availability authoring environment, role changes in Business Central are not saved [RHPAM-2342]

Issue: If you configure a role change in high-availability Business Central, the change can be lost after a time and the roles reset to defaults.

Workaround: Configure the role change again.

In a high-availability authoring environment, an imported project in Business Central appears multiple times [RHPAM-2372]

Issue: If you import a sample project in high-availability Business Central, the project can appear in the list several times. Some copies might not have all of the assets. The environment can slow down when this issue occurs.

Workaround: Ensure one copy has all of the assets, then remove all other copies. If Business Central performance is slow, restart all of the nodes connected to it.

In a high-availability authoring environment, project creation fails when a Business Central node is down [RHPAM-2475]

Issue: When you create a project, the project creation does not complete. The cause is one Business Central node in a high-availability authoring environment going down.

Workaround: Create the project again.

In a high-availability authoring environment, asset creation is not completed when a Business Central node is down [RHPAM-2476]

Issue: When you create an asset, the asset is not indexed. It is displayed in Business Central but you cannot use it. The cause is one Business Central node in a high-availability authoring environment going down.

Workaround: In the Project Explorer view, open the asset and click Save.

In a high-availability authoring environment, multi-project import slows down Business Central [RHPAM-2477]

Issue: When a user imports multiple projects in a high-availability Business Central with multi-project import enabled, Business Central slows down and consumes significant resources.

Steps to reproduce:

  1. In the Settings menu of Business Central, enable multi-project import.
  2. Enter a space and import all samples at one time.

Expected result: Business Central operates normally and imports the samples.

Actual result: Business Central slows down and consumes a lot of resources. In a Red Hat OpenShift Container Platform environment, the pod eventually fails.

Workaround: Restart all Business Central nodes. To avoid this issue, do not enable multi-project import.

5.4. Red Hat OpenShift Container Platform
复制链接

The role properties file configuration is available for internal authentication [RHPAM-2247]

Issue: The role properties file configuration should be available only when RH-SSO or LDAP authentication is used. However, currently it is also available when internal authentication is used.

Note

This issue is resolved with Red Hat Decision Manager patch release 7.5.1.

Steps to reproduce:

  1. Open the Business Automation Operator UI.
  2. Assign values to mandatory parameters.
  3. Retain the authentication mode Internal.
  4. Complete the role properties file configuration.
  5. Deploy the result.

Expected result: When internal authentication is used, it is not possible to specify the role properties file.

Actual result: When internal authentication is used, it is possible to specify the role properties file.

Workaround: If you plan to use internal authentication, leave the role properties file property in Business Automation Operator UI empty.

Resource requests have an incorrect name in the customer resource (CR) YAML file [RHPAM-2248]

Issue: Resource requests are specified as request in the Business Automation Operator UI, however in the customer resource definition (CRD) they are specified as requests. Therefore, CPU and memory requests from the UI are not applied.

Note

This issue is resolved with Red Hat Decision Manager patch release 7.5.1.

Steps to reproduce:

  1. Open the Business Automation Operator UI.
  2. Assign values to mandatory parameters.
  3. Complete CPU and memory requests for Console.
  4. Check the resulting YAML file.

Expected result: In the generated YAML file, resource requests are specified as requests.

Actual result: In the generated YAML file, resource requests are specified as request.

Workaround: In the generated YAML file, change the resource request specification from request to requests.

Product environment fails to deploy on Amazon Web Services (AWS) with AWS Elastic Block Storage (EBS) because of AWS EBS volume plugin lack of support for ReadWriteMany (RWX) persistent volume access mode [RHPAM-2480]

Issue: Several templates used for installing Red Hat Decision Manager on Red Hat OpenShift Container Platform, as well as deployment of several environment types using the Business Automation Operator, fail to deploy on AWS with EBS. The templates and environment types include persistent volume claims that require support for the ReadWriteMany access mode and the AWS EBS volume plugin does not provision persistent volumes with this access mode.

The rhdm75-authoring-ha.yaml template is affected.

Workaround: Deploy an NFS server and provision the persistent volumes using NFS. For information about provisioning persistent volumes using NFS, see one of the following guides:

Optaweb Vehicle Routing tests fail due to different versions of dependencies [RHDM-1129]

Issue: Optaweb Vehicle Routing is distributed with the incorrect package-lock.json file. As a result, snapshot tests of the optaweb-vehicle-routing-frontend module fail because of changes in HTML code generated by different versions of dependencies.

Workaround:

  1. Change directory to the optaweb-vehicle-routing-frontend module.

  2. Enter the following command to download the required dependencies: 

    $ npm install
    Copy to Clipboard Toggle word wrap

  3. Enter the following command to run the tests: 

    $ npm test
    Copy to Clipboard Toggle word wrap
  4. Press the u key to update failing snapshots.

The optaweb-employee-rostering example fails to build with the offline Maven repository ZIP files [RHPAM-2465]

Issue: When you build the optaweb-employee-rostering example with only Business Central and the Red Hat Decision Manager offline Maven repository, the build fails with the following message: 

Could not resolve dependencies for project org.optaweb.employeerostering:employee-rostering-server:jar:7.26.0.Final-redhat-00004: The following artifacts could not be resolved: net.jcip:jcip-annotations:jar:1.0.0.redhat-8, org.jboss.logging:jboss-logging:jar:3.3.2.Final-redhat-00001: Could not find artifact net.jcip:jcip-annotations:jar:1.0.0.redhat-8 in bxms-product-repo
Copy to Clipboard Toggle word wrap
Note

This issue is resolved with Red Hat Decision Manager patch release 7.5.1.

Workaround: Use the the Red Hat GA repository to fetch the missing artifacts.

Red Hat Business Optimizer is missing an environment variable for thread pool queue size [RHDM-1096]

Issue: The org.optaplanner.server.ext.thread.pool.queue.size system property has been added to the Decision Server Red Hat Business Optimizer extension. This property cannot be directly set on the Decision Server image.

Workaround: Use the existing JAVA_OPTS_APPEND environment variable and append the system property.

The Decision Server pod fails to start after a user updates the BusyBox image on Red Hat OpenShift Container Platform [RHPAM-2431]

Issue: In a Red Hat OpenShift Container Platform environment, a Decision Server pod fails to start or restart with the latest version of the BusyBox image.

Steps to reproduce:

  1. In your Red Hat OpenShift Container Platform environment, use a template or operator to deploy a Decision Server that uses a MySQL or PostgreSQL database server.

  2. Enter the following command to manually update the OpenShift registry to the latest BusyBox image: 

    $ docker pull busybox
    Copy to Clipboard Toggle word wrap
  3. Scale the Decision Server pod down to 0 replicas and then scale up.

Expected result: The Decision Server pod starts normally.

Actual result: The Decision Server pod fails to start and remains at 0 replicas.

Workaround:

  1. On a local machine that has access to the cluster and has Docker installed, enter the following command to pull the BusyBox image version 1.28.4: 

    $ docker pull docker.io/busybox:1.28.4
    Copy to Clipboard Toggle word wrap

  2. Enter the following comand to tag the image with the latest tag: 

    docker tag docker.io/busybox:1.28.4 myopenshiftcluster/openshift/busybox:latest
    Copy to Clipboard Toggle word wrap

  3. Push the image into your Red Hat OpenShift Container Platform environment. For instructions, refer to the following documentation:

High available event-driven decisioning (HA CEP server) build fails [RHPAM-2530]

Issue: The image build for the HA CEP server fails with the following message: 

The command '/bin/sh -c microdnf install --nodocs java-1.8.0-openjdk-headless && microdnf clean all' returned a non-zero code: 141
Copy to Clipboard Toggle word wrap

The probem is caused by a recently found issue with microdnf.

Workaround:

In the springboot directory, edit the Dockerfile file. Replace the line that contains the microdnf command with the following line: 

RUN microdnf install java-1.8.0-openjdk-headless && microdnf clean all
Copy to Clipboard Toggle word wrap
Red Hat logoGithubredditYoutubeTwitter

学习

尝试、购买和销售

社区

关于红帽文档

通过我们的产品和服务，以及可以信赖的内容，帮助红帽用户创新并实现他们的目标。 了解我们当前的更新.

让开源更具包容性

红帽致力于替换我们的代码、文档和 Web 属性中存在问题的语言。欲了解更多详情，请参阅红帽博客.

關於紅帽

我们提供强化的解决方案，使企业能够更轻松地跨平台和环境（从核心数据中心到网络边缘）工作。

Theme

© 2026 Red Hat返回顶部