Chapter 2. Known Issues

These are the known issues for Red Hat JBoss BRMS 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.
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.
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.
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 BRMS 6.4.10, enabling the Realtime Decision Server by uncommenting the block of system properties in standalone.xml results in Jackson deserialization failures, and the Realtime Decision 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.