9:18:34 PM at .(AbstractJavaResourceMethodDispatcher.java:79) 9:18:34 PM at .$TypeOutInvoker.doDispatch(JavaResourceMethodDispatcherProvider.java:219) 9:18:34 PM at .(AbstractJavaResourceMethodDispatcher.java:167) 9:18:34 PM at .$1.run(AbstractJavaResourceMethodDispatcher.java:124) 9:18:34 PM at .$static$0(ResourceMethodInvocationHandlerFactory.java:52)
9:18:34 PM at (DelegatingMethodAccessorImpl.java:43) 9:18:34 PM at (NativeMethodAccessorImpl.java:62) 9:18:34 PM at .ProcessDefinitionResourceImpl.startProcessInstance(ProcessDefinitionResourceImpl.java:131) Please check the server logs for a detailed message and the entire exception stack trace. 21:18:34.909 WARN 1 - .rest.exception : ENGINE-REST-HTTP500 .: Cannot instantiate process definition lg-customer-process:1:8d24c1ac-ada4-11eb-91ff-0a580a1404df: An exception occurred in the persistence layer. Here is the error I get when running a new instance. I suppose that there is a mechanism in the camunda project that maintains the new changes of the DB to keep it compatible with older versions like liquibase, is that right? Relation "act_ru_task_meter_log" does not exist I was running camunda engine 7.13 that was pulled from the docker image and it was running fine with Postgresql then moved to spring-boot camunda starter 7.15 but when I try to run a process instance of a deployed process, I get an incompatible DB schema issue which states that there is a missing relation.
0 kommentar(er)
