Chapter 2. Known Issues

These are the known issues for Red Hat JBoss BPM Suite 6.4:

[GPS] (6.4.z)Ability to specify priority for Asynchronous Tasks [RHBPMS-4778]
6.4 Update 6 introduces a small change into the database schema. You must apply the bpms-6.4-to-7.0.sql script to your database before you run Red Hat JBoss BPM Suite or Red Hat JBoss BRMS 6.4.6. This script is located in the upgrade-scripts/<database-type> directory, available from the Red Hat JBOSS BPM Suite 6.4 Update 6 and the Red Hat JBOSS BRMS 6.4 Update 6 zip files which you can download from the Red Hat Customer Portal.
When all next moves are not doable, optaplanner get stuck in step and if termination is not based on time, it cycles forever [RHBRMS-1726]
If the Business Resource Planner is in a state where all the entities are immovable, it gets stuck and only time based termination can terminate it. To workaround this issue, call the Solver.terminateEarly() method to break the cycle.
Installer doesn’t recognize EAP 7+ [RHBPMS-4269]
Installer cannot be used for installing Red Hat JBoss BPM Suite on Red Hat JBoss EAP 7. To install Red Hat JBoss BPM Suite on Red Hat JBoss EAP 7, use the deployable zip installation option.
Unable to extract update patch file on Windows [RHBPMS-1267]
The Red Hat JBoss BPM Suite patch zip file cannot be opened on Windows 7 with the Windows Explorer application. You can use third-party tools or the jar.exe -xvf <archived-patch-file> command to extract the zip file.
java.io.FileNotFoundException is thrown every time jBPM Designer is opened when Business Central is deployed on WebSphere [RHBPMS-40]
Opening a process definition in Business Central deployed on the WebSphere application server results in FileNotFoundException errors in the server log. There is currently no workaround for this issue.
Designer new commits doesn’t appear in "Latests Version" control [RHBPMS-290]
The Latest Version control does not reflect changes committed in processes or forms in Business Central. There is currently no workaround for this issue.
Transaction issues with Timer catch event [RHBPMS-4448]

If your application server is using the EJB executor to handle timer events, processes using singleton strategy may result in exceptions with the container managed transactions. This is caused by the EJB executor completing transaction outside of the KIE Session, which causes a race condition with another thread working with the same KIE Session. To work around this issue, use an executor bundled with Red Hat JBoss BPM Suite, which is aware of the singleton runtime strategy. To activate the bundled executor, set the system property org.kie.timer.ejb.disabled to true.

Alternatively, you can use the per process instance strategy where a new transaction is created for every invocation, or use the Quartz scheduler.

Start timer continue starting process instances after deactivating of deployment [RHBPMS-4389]
When you deactivate a deployment, the start event timers of its processes continue to fire and create new process instances. There is currently no workaround for this issue.
Container is not started when being created [RHBPMS-4375]

A container created using REST API or Business Central shows as Started in the Status field. However, it is not started until you explicitly stop and start it again in Business Central or make the following REST call:

POST http://localhost:8080/business-central/rest/controller/management/servers/default-kieserver/containers/org.jboss:integration:2.0.0-SNAPSHOT/status/started

The org.javassist:javassist:jar:3.19.0.GA-redhat-1 artifact used in optaplanner-core is missing from the Red Hat JBoss BPM Suite artifact repository. A workaround for this issue is to import the jboss-integration-platform-bom BOM.

Use of "contains" operator does not add values from enumeration with quotes in Guided Rules etc. [RHBRMS-2577]
When using enumeration for a field in guided rules, guided decision tables, or guided decision templates, the resulting rule does not contain the selected value from the enumeration drop down within quotes ("") resulting in validation errors. There is currently no workaround for this issue.
It is not possible to create Business Process on Windows server with I18n Business Process names [RHBPMS-2000], dashbuilder: Static data set definitions in WEB-INF/datasets dir not loaded on JWS3 (tomcat 8) [RHBPMS-850]
When Business Central is deployed on JBoss Web Server 3, the static data set definitions in WEB-INF/datasets are not loaded and no error messages appear in the log. There is currently no workaround for this issue.
Container resolved release id version is not changed after auto updated by scanner [RHBPMS-4437]
When a container is set to be auto updated by a scanner, the scanner does not replace the container when a new container version is deployed. There is currently no workaround for this issue.
If you change Business Central localization log out is required [RHBPMS-4425]
If you switch localization of Business Central, your language setting is not persistent. Opening the Business Central application in a new browser tab or window results in English settings. There is currently no workaround for this issue.
Jobs: Queued tab displays jobs in status DONE [RHBPMS-4246]
The jobs listed under the Queued tab in Business Central sometimes display as DONE in the Status column. This happens when you restore default filters and select the Queued tab immediately after that.
Business Central remote JMS client support for EAP7 [RHBPMS-4198]
Red Hat JBoss BPM Suite supports Business Central remote JMS clients on EAP 6.4 only.
AccessControlException when acessing Timeline [RHBPMS-4493]

Starting Business Central on Red Hat JBoss EAP 7 with the security manager enabled throws the AccessControlException error when you access your timeline. A workaround for this issue in a Linux environment is to add the following permissions to your kie.policy file:

permission java.io.FilePermission "/etc/gitconfig","read";
permission java.io.FilePermission "${user.home}/.gitconfig","read";
[GSS](6.4.z)Endpoint /history/clear not responsive [RHBPMS-4447]
The Business Central server may stop responding when clearing its history with more than 100 000 records in the log tables. To work around the issue, delete the tables directly in the database or use LogCleanupCommand from within a process that can accept different parameters in the Intelligent Process Server. Alternatively, for the Business Central server, register the asynchronous Work Item Handler, use it to call LogCleanupCommand and start the process using the KIE runtime API.
Quartz timer retry issue [RHBPMS-4431]
Database or network issues may cause the quartz trigger to fail for more than five times. This may result in the process workflow stopping, or the Quartz trigger deletion. There is no workaround for this issue.
Forms new commits doesn’t appear in "Latests Version" control [RHBPMS-4239]
The Latest Version control does not reflect changes committed in Business Central. There is currently no workaround for this issue.
Remove Russian and Chinese (Traditional) from language dropdown [RHBPMS-4430]

The Dashbuilder does not list Simplified Chinese in the language drop down list. To work around this issue, set the following system property into the application server:

LocaleManager.installedLocaleIds=en,es,de,fr,pt,ja,zh

Alternatively, you can start your server and set this property as a command line parameter.

Null Pointer exception occurs for Business Process with empty Embedded SubProcess [RHBPMS-4514]
Simulating processes with empty embedded subprocess throw NullPointerException. There is currently no workaround for this issue.
Backward-incompatible change in ModifyCommand [RHBRMS-2703]
The JAXB marshalled form of org.drools.core.command.runtime.rule.ModifyCommand has changed and is backward incompatible. If you are creating an XML for marshalled command manually, you need to modify the attributes annotated by JAXB for marshalling in the XML. For more information, see the Migrating from 6.X to 6.4 section of the Red Hat JBoss BPM Suite 6.4 Migration Guide.
Dashbuilder must use the same datasource as Business Central [RHBPMS-4517]
Configuring different datasources for Business Central and Dashbuilder may lead to Dashbuilder having no visibility to default tables, processes and tasks started on Business Central. There is currently no workaround for these issues arising due to configuring separate datasources for Business Central and Dashbuilder.
Managed KIE Servers do not work with latest Red Hat JBoss EAP security patch for Jackson [RHBPMS-5192]

When using Red Hat JBoss EAP 6.4.20 with Red Hat JBoss BPM Suite 6.4.10, enabling the Intelligent Process Server by uncommenting the block of system properties in standalone.xml results in Jackson deserialization failures, and the Intelligent Process Server fails to deploy in Business Central. This is caused by a Jackson fix introduced in the Red Hat JBoss EAP 6.4.20 patch. For more information, see the JBoss Enterprise Application Platform 6.4 Update 20 Release Notes.

To protect Red Hat JBoss EAP 6.4.20 from Jackson databind deserialization vulnerabilities, you must start the server with the following system properties:

 -Djackson.deserialization.whitelist.packages=

Using an empty string allows all classes for serialization. This setting is insecure and not recommended in production.

 -Djackson.deserialization.whitelist.packages=org.kie,org.drools,other.custom.package

For a secure configuration, add all of the packages in a comma separated list to the property which needs to be serialized. The org.kie and org.drools packages are mandatory.