Deployed Sample Process Not Showing up in Cockpit

Hi Team,

I would appreciate commenting on my issue.

I have read lots of similar requests and it seems checked and fixed all offered solutions but can not get sample process to appear in Cockpit.

Thanks!

I am passing this tutorial, getting sample files from github

JDK-13.0.2 enabled

Log

13-Feb-2020 21:19:10.766 INFO [localhost-startStop-2] org.apache.catalina.startup.HostConfig.deployWAR Deploying web application archive [/var/lib/tomcat/webapps/loan-approval-0.1.0-SNAPSHOT.war]
13-Feb-2020 21:19:17.768 INFO [localhost-startStop-2] org.apache.jasper.servlet.TldScanner.scanJars At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
13-Feb-2020 21:19:17.810 INFO [localhost-startStop-2] org.apache.catalina.startup.HostConfig.deployWAR Deployment of web application archive [/var/lib/tomcat/webapps/loan-approval-0.1.0-SNAPSHOT.war] has finished in [7,043] ms
13-Feb-2020 21:50:11.429 INFO [ContainerBackgroundProcessor[StandardEngine[Catalina]]] org.apache.catalina.startup.HostConfig.undeploy Undeploying context [/loan-approval-0.1.0-SNAPSHOT]
13-Feb-2020 21:50:11.491 INFO [localhost-startStop-3] org.apache.catalina.startup.HostConfig.deployWAR Deploying web application archive [/var/lib/tomcat/webapps/loan-approval-0.1.0-SNAPSHOT.war]
13-Feb-2020 21:50:11.901 INFO [localhost-startStop-3] org.apache.jasper.servlet.TldScanner.scanJars At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
13-Feb-2020 21:50:11.915 INFO [localhost-startStop-3] org.apache.catalina.startup.HostConfig.deployWAR Deployment of web application archive [/var/lib/tomcat/webapps/loan-approval-0.1.0-SNAPSHOT.war] has finished in [424] ms
13-Feb-2020 21:53:42.393 INFO [ContainerBackgroundProcessor[StandardEngine[Catalina]]] org.apache.catalina.startup.HostConfig.undeploy Undeploying context [/loan-approval-0.1.0-SNAPSHOT]
13-Feb-2020 21:53:42.761 INFO [localhost-startStop-4] org.apache.catalina.startup.HostConfig.deployWAR Deploying web application archive [/var/lib/tomcat/webapps/loan-approval-0.1.0-SNAPSHOT.war]
13-Feb-2020 21:53:48.776 INFO [localhost-startStop-4] org.apache.jasper.servlet.TldScanner.scanJars At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
13-Feb-2020 21:53:48.940 INFO [localhost-startStop-4] org.apache.catalina.startup.HostConfig.deployWAR Deployment of web application archive [/var/lib/tomcat/webapps/loan-approval-0.1.0-SNAPSHOT.war] has finished in [6,178] ms

Project structure

Screenshot_15

Please check if the WAR file you copied into …\camunda-bpm-tomcat-7.12.0\server\apache-tomcat-9.0.24\webapps contains`
- processes.xml in WEB-INF\classes\META-INF
- loan-approval.bpmn in WEB_INF\classes

If this is the case, you should see something like:

14-Feb-2020 15:49:57.078 INFO [Catalina-utility-1] org.camunda.commons.logging.BaseLogger.logInfo ENGINE-08024 Found processes.xml file at file:/C:/install/camunda-bpm-tomcat-7.12.0/server/apache-tomcat-9.0.24/webapps/loan-approval-0.1.0-SNAPSHOT/WEB-INF/classes/META-INF/processes.xml
14-Feb-2020 15:49:57.082 INFO [Catalina-utility-1] org.camunda.commons.logging.BaseLogger.logInfo ENGINE-08023 Deployment summary for process archive 'loan-approval':

        loan-approval.bpmn

14-Feb-2020 15:49:57.101 INFO [Catalina-utility-1] org.camunda.commons.logging.BaseLogger.logInfo ENGINE-07021 ProcessApplication 'Loan Approval App' registered for DB deployments [983a796e-4efe-11ea-891f-9c899b574756]. Will execute process definitions

        approve-loan[version: 1, id: approve-loan:1:983cc360-4efe-11ea-891f-9c899b574756]

If it is not the case, try a maven clean and package: mvn clean package to rebuild the war and deploy it again.

Thanks for your answer

processes.xml and .bpmn are present in war file. I check them each time
All build instructions i.e. mvn install, mvn clean install, mvn package, mvn clean package produce exactly the same not working result.

Also I tried pure mvn with jdk without Eclipse

I have never been able to see rows
loan-approval.bpmn
or
approve-loan[version: 1, id: approve-loan:1:983cc360-4efe-11ea-891f-9c899b574756]
in catalina.out logs

Sorry, from you answer it is not clear to me if the WAR which is built contains the file in the mentioned folders. Does it?

  • processes.xml in WEB-INF\classes\META-INF
  • loan-approval.bpmn in WEB_INF\classes

Yes, both files are present in war archive in specified folders.
Also they were present during previous attempts

Sorry to ask again… The screenshot only showed the project. Did you also open the war file (e.g. with 7zip) and check if the files are included there? In the startup log you see camunda output?

No problem, I appreciate your help
Yes, I checked unzipped file
Log file each time shows only same rows I posted above
I found about 8 same ‘deployed war processes can not be seen in Cockpit’ cases on forum and tried their solutions. Checking xml and bpmn files is one of first steps which I have already done

image

My Camunda implementation is made on AWS EC2 instance with AMI Linux 2 and Tomcat 8.5.50. Hope this information could be useful

I was just going to ask which tomcat installation you are using. You need to use a tomcat installation which includes Camunda, as described here: https://docs.camunda.org/get-started/java-process-app/install/

First, download a distribution of the Camunda BPM platform. You can choose from different distributions for various application servers. In this tutorial, we will use the Apache Tomcat based distribution. Download it from the download page.

The WAR you are deploying is only a few kb and packages only the specific process application. The engine is packaged in the camunda web aplication, which is par of the tomcat. image

However, if you plan to deploy on AWS and do not want to use the prepackaged tomcat distribution, then you can also consider the Spring boot getting started here: https://docs.camunda.org/get-started/spring-boot/ This will build you a complete process application including engine and server.

If you are not familiar with Maven / Java then
https://hub.docker.com/r/camunda/camunda-bpm-platform/

docker pull camunda/camunda-bpm-platform:latest
docker run -d --name camunda -p 8080:8080 camunda/camunda-bpm-platform:latest
# open browser with url: http://localhost:8080/camunda-welcome/index.html

might be an option you are more comfortable with.

Once you have a running engine / server, you can also deploy process models directly from the modeler, via REST to it.

Thank you, that shows possible ways to proceed. I will try
Could you please also advise how bpmn process deployment should look like if Camunda is installed as standalone version from precompiled war file?

The startup with pre-packaged Camunda (camunda-bpm-tomcat-7.12.0)
I showed above. You mean a Spring boot startup?

Spring-Boot: (v2.2.1.RELEASE)
Camunda BPM: (v7.12.0)
Camunda BPM Spring Boot Starter: (v3.4.1)

2020-02-17 15:29:33.920 INFO 15728 — [ main] com.example.workflow.Application : Starting Application on LAPTOP-NHIKAJ44 with PID 15728 (C:\dev\my-project\target\classes started by [~] in C:\dev\my-project)
2020-02-17 15:29:33.923 INFO 15728 — [ main] com.example.workflow.Application : No active profile set, falling back to default profiles: default
2020-02-17 15:29:34.596 INFO 15728 — [ main] .s.d.r.c.RepositoryConfigurationDelegate : Bootstrapping Spring Data repositories in DEFAULT mode.
2020-02-17 15:29:34.621 INFO 15728 — [ main] .s.d.r.c.RepositoryConfigurationDelegate : Finished Spring Data repository scanning in 8ms. Found 0 repository interfaces.
2020-02-17 15:29:34.799 INFO 15728 — [ main] trationDelegate$BeanPostProcessorChecker : Bean ‘org.springframework.transaction.annotation.ProxyTransactionManagementConfiguration’ of type [org.springframework.transaction.annotation.ProxyTransactionManagementConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2020-02-17 15:29:34.949 INFO 15728 — [ main] o.s.b.w.embedded.tomcat.TomcatWebServer : Tomcat initialized with port(s): 8080 (http)
2020-02-17 15:29:34.954 INFO 15728 — [ main] o.apache.catalina.core.StandardService : Starting service [Tomcat]
2020-02-17 15:29:34.955 INFO 15728 — [ main] org.apache.catalina.core.StandardEngine : Starting Servlet engine: [Apache Tomcat/9.0.27]
2020-02-17 15:29:35.053 INFO 15728 — [ main] o.a.c.c.C.[Tomcat].[localhost].[/] : Initializing Spring embedded WebApplicationContext
2020-02-17 15:29:35.053 INFO 15728 — [ main] o.s.web.context.ContextLoader : Root WebApplicationContext: initialization completed in 1087 ms
2020-02-17 15:29:35.067 INFO 15728 — [ main] .c.b.s.b.s.r.CamundaJerseyResourceConfig : Configuring camunda rest api.
2020-02-17 15:29:35.077 INFO 15728 — [ main] .c.b.s.b.s.r.CamundaJerseyResourceConfig : Finished configuring camunda rest api.
2020-02-17 15:29:35.251 INFO 15728 — [ main] com.zaxxer.hikari.HikariDataSource : HikariPool-1 - Starting…
2020-02-17 15:29:35.392 INFO 15728 — [ main] com.zaxxer.hikari.HikariDataSource : HikariPool-1 - Start completed.
2020-02-17 15:29:35.418 INFO 15728 — [ main] o.hibernate.jpa.internal.util.LogHelper : HHH000204: Processing PersistenceUnitInfo [name: default]
2020-02-17 15:29:35.466 INFO 15728 — [ main] org.hibernate.Version : HHH000412: Hibernate Core {5.4.8.Final}
2020-02-17 15:29:35.559 INFO 15728 — [ main] o.hibernate.annotations.common.Version : HCANN000001: Hibernate Commons Annotations {5.1.0.Final}
2020-02-17 15:29:35.636 INFO 15728 — [ main] org.hibernate.dialect.Dialect : HHH000400: Using dialect: org.hibernate.dialect.H2Dialect
2020-02-17 15:29:35.776 INFO 15728 — [ main] o.h.e.t.j.p.i.JtaPlatformInitiator : HHH000490: Using JtaPlatform implementation: [org.hibernate.engine.transaction.jta.platform.internal.NoJtaPlatform]
2020-02-17 15:29:35.781 INFO 15728 — [ main] j.LocalContainerEntityManagerFactoryBean : Initialized JPA EntityManagerFactory for persistence unit ‘default’
2020-02-17 15:29:35.803 WARN 15728 — [ main] JpaBaseConfiguration$JpaWebConfiguration : spring.jpa.open-in-view is enabled by default. Therefore, database queries may be performed during view rendering. Explicitly configure spring.jpa.open-in-view to disable this warning
2020-02-17 15:29:36.052 INFO 15728 — [ main] org.camunda.bpm.spring.boot : STARTER-SB040 Setting up jobExecutor with corePoolSize=3, maxPoolSize:10
2020-02-17 15:29:36.053 INFO 15728 — [ main] o.s.s.concurrent.ThreadPoolTaskExecutor : Initializing ExecutorService ‘camundaTaskExecutor’
2020-02-17 15:29:36.098 INFO 15728 — [ main] org.camunda.bpm.engine.cfg : ENGINE-12003 Plugin ‘CompositeProcessEnginePlugin[genericPropertiesConfiguration, camundaProcessEngineConfiguration, camundaDatasourceConfiguration, camundaJpaConfiguration, camundaJobConfiguration, camundaHistoryConfiguration, camundaMetricsConfiguration, camundaAuthorizationConfiguration, camundaDeploymentConfiguration, CreateAdminUserConfiguration[adminUser=AdminUserProperty[id=demo, firstName=Demo, lastName=Demo, email=demo@localhost, password=******]], failedJobConfiguration, eventPublisherPlugin]’ activated on process engine ‘default’
2020-02-17 15:29:36.797 WARN 15728 — [ main] s.b.s.c.i.DefaultDeploymentConfiguration : unable to determine if resource URL [jar:file:C:\Users[~].m2\repository\org\camunda\bpm\dmn\camunda-engine-dmn\7.12.0\camunda-engine-dmn-7.12.0.jar!/META-INF/maven/org.camunda.bpm.dmn/] is a deployable resource
2020-02-17 15:29:36.797 WARN 15728 — [ main] s.b.s.c.i.DefaultDeploymentConfiguration : unable to determine if resource URL [jar:file:C:\Users[~].m2\repository\org\camunda\bpm\dmn\camunda-engine-feel-api\7.12.0\camunda-engine-feel-api-7.12.0.jar!/META-INF/maven/org.camunda.bpm.dmn/] is a deployable resource
2020-02-17 15:29:36.797 WARN 15728 — [ main] s.b.s.c.i.DefaultDeploymentConfiguration : unable to determine if resource URL [jar:file:C:\Users[~].m2\repository\org\camunda\bpm\dmn\camunda-engine-feel-juel\7.12.0\camunda-engine-feel-juel-7.12.0.jar!/META-INF/maven/org.camunda.bpm.dmn/] is a deployable resource
2020-02-17 15:29:36.797 INFO 15728 — [ main] org.camunda.bpm.spring.boot : STARTER-SB021 Auto-Deploying resources: [file [C:\dev\my-project\target\classes\ParallelABCExternal.bpmn]]
2020-02-17 15:29:36.799 INFO 15728 — [ main] o.c.b.s.b.s.event.EventPublisherPlugin : EVENTING-001: Initialized Camunda Spring Boot Eventing Engine Plugin.
2020-02-17 15:29:36.799 INFO 15728 — [ main] o.c.b.s.b.s.event.EventPublisherPlugin : EVENTING-003: Task events will be published as Spring Events.
2020-02-17 15:29:36.799 INFO 15728 — [ main] o.c.b.s.b.s.event.EventPublisherPlugin : EVENTING-005: Execution events will be published as Spring Events.
2020-02-17 15:29:36.800 INFO 15728 — [ main] o.c.b.s.b.s.event.EventPublisherPlugin : EVENTING-007: History events will be published as Spring events.
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.apache.ibatis.reflection.Reflector (file:/C:/Users/[~]/.m2/repository/org/mybatis/mybatis/3.4.4/mybatis-3.4.4.jar) to method java.lang.Object.finalize()
WARNING: Please consider reporting this to the maintainers of org.apache.ibatis.reflection.Reflector
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
2020-02-17 15:29:39.958 INFO 15728 — [ main] org.camunda.bpm.engine : ENGINE-00001 Process Engine default created.
2020-02-17 15:29:39.976 INFO 15728 — [ main] org.camunda.bpm.spring.boot : STARTER-SB011 skip creating initial Admin User, user does exist: UserEntity[id=demo, revision=1, firstName=Demo, lastName=Demo, email=demo@localhost, password={SHA-512}Hffw9NJ3E6faTMx+MOvaJ/OYMsFvhxlTFAAuG0BesZQ9UROlgft78LSglA51NwcauDvRO8hXsUj3HndYrm7ryQ==, salt=x4GyKcDB9DbtL3v5LQh1ww==, lockExpirationTime=null, attempts=0]
2020-02-17 15:29:40.148 INFO 15728 — [ main] o.c.b.s.b.s.w.f.LazyInitRegistration : lazy initialized org.camunda.bpm.spring.boot.starter.webapp.filter.LazyProcessEnginesFilter@161aa04a
2020-02-17 15:29:40.183 INFO 15728 — [ main] o.c.b.s.b.s.w.f.LazyInitRegistration : lazy initialized org.camunda.bpm.spring.boot.starter.webapp.filter.LazySecurityFilter@67f77f6e
2020-02-17 15:29:40.471 INFO 15728 — [ main] o.s.b.w.embedded.tomcat.TomcatWebServer : Tomcat started on port(s): 8080 (http) with context path ‘’
2020-02-17 15:29:40.474 INFO 15728 — [ main] com.example.workflow.Application : Started Application in 6.868 seconds (JVM running for 7.681)
2020-02-17 15:29:40.475 INFO 15728 — [ main] org.camunda.bpm.engine.jobexecutor : ENGINE-14014 Starting up the JobExecutor[org.camunda.bpm.engine.spring.components.jobexecutor.SpringJobExecutor].
2020-02-17 15:29:40.476 INFO 15728 — [ingJobExecutor]] org.camunda.bpm.engine.jobexecutor : ENGINE-14018 JobExecutor[org.camunda.bpm.engine.spring.components.jobexecutor.SpringJobExecutor] starting to acquire jobs

Thanks for your help, I will try one of above methods

@ rob2universe thanks for your help.
Everything works fine, demo processes are deploying well
Regards