-
Bug Report
-
Resolution: Cannot Reproduce
-
L3 - Default
-
None
-
None
-
None
-
Deployment of camunda-engine 7.13.0 within a Wildfly 11 AS as an EAR-Deployment
After updating from camunda 7.6.0 to 7.13.0 we get the attached exception.
In our code, we are executing a query for a process definition as follows:
org.camunda.bpm.engine.RepositoryService
.createProcessDefinitionQuery()
.processDefinitionKey(pProcessDefinitionKey)
.latestVersion()
.singleResult();
While debugging, it can be seen, that somwhere in the code an internal "orderBy" is entered, which is set to order along the ID-Column of the result.
This Bug (https://jira.camunda.com/browse/CAM-6376) might be related or not, I did a manual downgrade of mybatis (i.e. replacing 3.5.3 with 3.2.8 from Camunda 7.6.0 in my Deployment), which did not change the issue.
This is the controller panel for Smart Panels app
[CAM-12505] Missing property 'orderBy' in 'class org.camunda.bpm.engine.impl.ProcessDefinitionQueryImpl'
I would like to put this issue on hold at the moment. I have discovered, that this might be related to some modifications we made to the DbSqlSessionFactory.
Hi Jonathan,
Thank you for notifying us! I tried to reproduce the issue today but wasn't able to.
Therefore, I will close this ticket. Feel free to ping us here if you can reproduce the bug in the future, and we will re-open the ticket.
Best,
Nikola
Just for the record:
Camunda renamed the property "orderBy" to "internalOrderBy". Therefore, if you had set "databaseSpecificOrderByStatements" (in DbSqlSessionFactory) with a reference to ${orderBy} this broke somewhere between 7.6 and 7.13. The solution is to change the JUEL to ${internalOrderBy}.
In case someone from Camunda reads this: Is there any documentation, where such changes are kept on record? (No hard feelings, just checking whether there would have been a less painful way to resolve this)
Hi Jonathan,
Thank you for the report. As we are currently in the middle of testing the next minor release (7.14.0), classifying this ticket might take a couple more days. By the end of the week, I will try to reproduce the issue and will ping you if I need more details.
Best,
Nikola