Chapter 2. Known Issues

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

Race condition with multiple job executor threads on Oracle [RHBPMS-1116]
When using the AsyncWorkItemHandler class with Oracle Database, a job can be picked up by two threads if the thread pool is larger than one. For queries which use rownum + for update, Hibernate breaks the query in two. This allows for the same job being processed by different AvailableJobsExecutor threads. To work around the issue, use custom dialect Oracle10gDialect that disables follow on locking and allows you to configure initial delay of executor work threads so they are not firing at exactly the same time.
dashbuilder: Static data set definitions in WEB-INF/datasets dir not loaded on JWS3 (tomcat 8) [RHBPMS-850]
When you deploy Business Central on Red Hat JBoss Web Server 3, static Dashbuilder dataset definitions placed in the WEB-INF/datasets directory are not loaded. There is currently no workaround. Note that the ability to create dataset definitions in the Dataset editor (Extensions → Data Sets) is not affected.
Deployment of the kie artifacts (or kjars) using FluentKieModuleDeploymentHelper deploys only to local .m2 repository only [RHBRMS-1928]
Deploying KIE artifacts or kJARs using the FluentModuleDeploymentHelper class is not possible to remote Maven repositories, only to the local Maven repository (.m2). There is currently no workaround.
Tag filtering slows down performance of the Authoring perspective considerably [RHBRMS-2253]
Enabling tag filtering in Business Central’s Authoring perspective results in degraded performance and can severely impact the operation of Project Explorer for large projects. There is currently no workaround.
It is not possible to create Business Process on Windows server with I18n Business Process names [RHBPMS-2000]

Due to a wrong file encoding, it is impossible to create assets with i18n names (for example 日本語 or Русский) when running Red Hat JBoss BPM Suite on Windows. To work around the issue, set the file encoding of your application server to UTF8, for example: 

set "JAVA_OPTS=-Dfile.encoding=UTF-8 -Dprogram.name=%PROGNAME% %JAVA_OPTS%"

in the Red Hat JBoss EAP standalone.bat within the :Main label.

kie-aries-blueprint does not define ksession-ref and kbase-ref elements in XSD [RHBRMS-2322]

The elements <ksession-ref> and <kbase-ref> can not be used with KIE-Aries-Blueprint, because they are only partially implemented, and are not defined in kie-aries-blueprint.xsd. These elements are used for declaring Blueprint beans for KieSession or KieBase from a kJAR with a given ReleaseId. Their usage currently results in Blueprint rejecting the given XML. To work around the problem, declare a bean for KieContainer, and use that for creating KieSession or KieBase beans manually as follows: 

<kie:kcontainer-ref id="kjar-kcontainer" releaseId="kjar-gav" />

<bean id="kieSessionBean"
      factory-ref="kjar-kcontainer"
      factory-method="newKieSession"
      destroy-method="dispose">
  <argument value="kieSessionName"/>
</bean>
OptaPlanner Kie server: Cannot marshall best solution score [RHBRMS-1399]
The Realtime Decision Server is unable to correctly marshall the score of Business Resource Planner’s best solution. The best solution’s score is incorrectly unmarshalled—​The response contains an empty score or a score with the default value. The affected marshalling formats are JAXB (the functionality is entirely unavailable) and JSON (the only unmarshallable classes are BendableLongScore, BendableBigDecimalScore, and BendableScore). The XSTREAM format is not affected. There is currently no workaround.