Red Hat Bugzilla – Bug 1271210
SQL command not properly ended on Oracle11
Last modified: 2015-10-21 09:28:20 EDT
Created attachment 1082356 [details]
Description of problem:
Business Central is not deployed due to SQL exceptions (see the attached server.log) after I create schema based on:
Business Central is configured to use org.jbpm.persistence.jpa.hibernate.DisabledFollowOnLockOracle10gDialect
Another alternative is to start Business Central with empty database and then run process instances with human task simultaneously in 16 threads - the same exceptions occur when the clients try to complete their tasks. However, the easiest way to reproduce the problem is described above. I believe that the processes then fail because of the missing indexes....
since JMS based executor has been introduced the org.jbpm.persistence.jpa.hibernate.DisabledFollowOnLockOracle10gDialect should not be used as it was considered just a workaround when many executor threads were configured. Since this is not needed any more standard oracle dialect should be used.
Can you please try to run it with standard Oracle dialect instead.
After further investigation of the attached log the problem is that kie server is deployed and apparently ExampleDS is Oracle data source while kie server has not been configured for Oracle and still uses H2 dialect and thus sql not properly ended error.
Make sure to configure data source and dialed for Kie Server using system properties:
Please also note that it is recommended to use different data sources (db schemas) for business central and kie server to avoid any unexpected behavior.
OK, I confirm that the recommended changes to KIE server helped. Thank you, Maciej. ... so closing the issue.