I just upgraded from 7.3 to 7.4.
The step I did are the following:
-dowloaded 7.4 distribution
-merged all folders and removed all old jars on my jboss (6.3 EAP).
-Cleared datasource (shared process engine) with a script (DROP TABLE table_name CASCADE CONSTRAINTS; for each table)
-redeployed webapp7.4
By doing this, I get a regenerated Process Engine but when I deploy webapp 7.4 nothing is accessible. Not able to set my admin account and of course no cockpit, tasklist…and there is a label in the top-right corner “{{currentEngine.name}}”.
I tried to redeploy webapp7.3 and this way I can set again the main admin user and see new deployments.
New deployments, if selected, throw a server error (NoSuchMethodException) related to jar conflicts I guess.
Then, if I redeploy webapp7.4 everything seems to be fixed but if I launch a new process, the diagram displays the current task in which the process is but the process instance itself is not accessible.
It means that it is not in the list of actives p.i. so no process variable is accessible/available etc…
this is the stack trace I get when I try to retrieve p.i. from webapp7.3 and the server run with camunda 7.4.
Caused by: java.lang.NoSuchMethodError: org.camunda.bpm.cockpit.db.QueryParameters.getPermissionChecks()Ljava/util/List; at org.camunda.bpm.cockpit.plugin.resource.AbstractCockpitPluginResource.configureAuthorizationCheck(AbstractCockpitPluginResource.java:82) [camunda-webapp-core-7.3.0.jar:7.3.0] at org.camunda.bpm.cockpit.impl.plugin.base.resources.ProcessInstanceRestService.configureExecutionQuery(ProcessInstanceRestService.java:129) [classes:] at org.camunda.bpm.cockpit.impl.plugin.base.resources.ProcessInstanceRestService$2.execute(ProcessInstanceRestService.java:99) [classes:] at org.camunda.bpm.cockpit.impl.plugin.base.resources.ProcessInstanceRestService$2.execute(ProcessInstanceRestService.java:96) [classes:] at org.camunda.bpm.engine.impl.interceptor.CommandExecutorImpl.execute(CommandExecutorImpl.java:24) [camunda-engine-7.4.0.jar:7.4.0] at org.camunda.bpm.engine.impl.interceptor.CommandContextInterceptor.execute(CommandContextInterceptor.java:95) [camunda-engine-7.4.0.jar:7.4.0] at org.camunda.bpm.engine.impl.interceptor.LogInterceptor.execute(LogInterceptor.java:30) [camunda-engine-7.4.0.jar:7.4.0] at org.camunda.bpm.cockpit.impl.db.CommandExecutorImpl.executeCommand(CommandExecutorImpl.java:39) [camunda-webapp-core-7.3.0.jar:7.3.0] at org.camunda.bpm.cockpit.impl.plugin.base.resources.ProcessInstanceRestService.queryProcessInstancesCount(ProcessInstanceRestService.java:96) [classes:] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.8.0_60] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [rt.jar:1.8.0_60] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_60] at java.lang.reflect.Method.invoke(Method.java:497) [rt.jar:1.8.0_60] at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:167) [resteasy-jaxrs-2.3.8.SP4-redhat-2.jar:] at org.jboss.resteasy.core.ResourceMethod.invokeOnTarget(ResourceMethod.java:269) [resteasy-jaxrs-2.3.8.SP4-redhat-2.jar:] at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:227) [resteasy-jaxrs-2.3.8.SP4-redhat-2.jar:] at org.jboss.resteasy.core.ResourceLocator.invokeOnTargetObject(ResourceLocator.java:159) [resteasy-jaxrs-2.3.8.SP4-redhat-2.jar:] at org.jboss.resteasy.core.ResourceLocator.invoke(ResourceLocator.java:92) [resteasy-jaxrs-2.3.8.SP4-redhat-2.jar:] at org.jboss.resteasy.core.SynchronousDispatcher.getResponse(SynchronousDispatcher.java:542) [resteasy-jaxrs-2.3.8.SP4-redhat-2.jar:] ... 32 more
I get an exception just while using webapp7.3 and camunda 7.4 version on jboss.
I use the normal one (camunda-webapp-jboss-7.X.0.war).
This exception is thrown because we do not guarantee backward-compatibility for the web applications with newer engine versions. Could you please try the WebApp 7.4 with your 7.4 installation.
Edit: We should focus on getting the WebApp 7.4 running with your 7.4 installation. Could you please add the exceptions / server logs when deploying them together?
That’s the point, maybe I didn’t explain it clearly in the first post.
I first deployed webapp7.4 in a server running camunda7.4 but that led me to a not usable webapp. I’m neither allowed to set up the admin user for accessing apps.
So I tried to redeploy webapp7.3 and that partially fixed the problem.
I was able to set the admin user but I got a problem when I tried to use the cockpit (which as you also said is quite normal because of not complete backwards compatibility).
The fact of setting the admin user allowed me, once I redeployed webapp7.4, to log in and access the cockipt without getting any error. The problem now is that deployments are there but actives p.i. are not in the the list they should be.
Could you please open up the network tab of your browser and check that no requests are running into an error?
Besides that, why did you drop the database tables when upgrading from 7.3 to 7.4. We provide migration scripts to upgrade between minor versions.
angular.js:9778Error: [$injector:unpr] Unknown provider: routeUtilProvider <- routeUtil http://errors.angularjs.org/1.2.16/$injector/unpr?p0=routeUtilProvider%20%3C-%20routeUtil at angular.js:78 at angular.js:3705 at Object.n [as get] (angular.js:3832) at angular.js:3710 at n (angular.js:3832) at r (angular.js:3859) at Object.i [as instantiate] (angular.js:3880) at angular.js:7134 at camunda-bpm-sdk-angular.js:5567 at c (angular.js:11319)(anonymous function) @ angular.js:9778
I dropped the DB because I’m also testing deployments and for having a clean environment I had to remove manually old process definitions.
That led me to a weird Engine status.
I know that the recommended way is via repository API but I don’t have the time now to build code for that purpose.
So I thought to reset the engine through sql.
And I also wanted to keep a sort of recovery copy of the DB (an empty one, just the structure).
That error looks like it is related to caching of the webapp like @thorben mentioned above. Please clear the browser cache or start the webapp in browser private mode and try again.
For an unknown reason the list is now filled.
I just cleared the debug console an refreshed the page.
Now, the question is why I got that error?
By resetting the Engine I thought I would have had a clean environment.
Instead webapp7.4 was not working and I had to deploy the previous version of webapp for solving.
Any idea on what could be the problem?
It is quite possible that I have to re-do the procedure again but, if possible, I would like to avoid to deploy webapp7.3 for fixing.
