Hi,
I was using postgres database with auto-generated tables using camunda-springboot-starter(3.4.0).
When clicking Cockpit/Tasklist/Admin link that always shows loading icon.
There have 404 errors for loading plugin.js and plugin.css.
From the info given it is hard to analyze. Have you had a look at the startup / log?
In this project I had created two Camunda instances against Postgres with Spring Boot. Do you want to try if this project works on your env or compare your config?
There are some screenshots with errors.
Server startup log? Did you get a chance to run or compare the example I provided?
user@user-PC:/media/user/_dde_data/vscode_projects/crusoefo$ /usr/lib/jvm/java-8-openjdk-amd64/bin/java -Dfile.encoding=UTF-8 -cp /tmp/cp_edtkyipl436jj5d6whz3bybm9.jar com.crusoe.fo.App
2020-02-24 20:56:47.722 INFO 18925 — [ main] trationDelegate$BeanPostProcessorChecker : Bean ‘org.springframework.cloud.autoconfigure.ConfigurationPropertiesRebinderAutoConfiguration’ of type [org.springframework.cloud.autoconfigure.ConfigurationPropertiesRebinderAutoConfiguration$$EnhancerBySpringCGLIB$$a84cc90f] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
/ | __ _ _ __ ___ _ _ _ __ | | __ _ | __ )| _ | / |
| | / | '_ _ | | | | ’ \ / |/ _ | | _ | |) | |/| |
| || (| | | | | | | || | | | | (| | (| | | |) | /| | | |
_/_,|| || ||_,|| ||_,|_,| |_/|| || ||
Spring-Boot: (v2.2.1.RELEASE)
Camunda BPM: (v7.12.0)
Camunda BPM Spring Boot Starter: (v3.4.0)
2020-02-24 20:56:47.923 INFO 18925 — [ main] c.c.c.ConfigServicePropertySourceLocator : Fetching config from server at : http://localhost:8888
2020-02-24 20:56:48.020 INFO 18925 — [ main] c.c.c.ConfigServicePropertySourceLocator : Connect Timeout Exception on Url - http://localhost:8888. Will be trying the next url if available
2020-02-24 20:56:48.021 WARN 18925 — [ main] c.c.c.ConfigServicePropertySourceLocator : Could not locate PropertySource: I/O error on GET request for “http://localhost:8888/camunda-service/default”: 拒绝连接 (Connection refused); nested exception is java.net.ConnectException: 拒绝连接 (Connection refused)
2020-02-24 20:56:48.025 INFO 18925 — [ main] com.crusoe.fo.App : No active profile set, falling back to default profiles: default
2020-02-24 20:56:49.062 INFO 18925 — [ main] .s.d.r.c.RepositoryConfigurationDelegate : Bootstrapping Spring Data repositories in DEFAULT mode.
2020-02-24 20:56:49.093 INFO 18925 — [ main] .s.d.r.c.RepositoryConfigurationDelegate : Finished Spring Data repository scanning in 18ms. Found 0 repository interfaces.
2020-02-24 20:56:49.246 WARN 18925 — [ main] o.s.boot.actuate.endpoint.EndpointId : Endpoint ID ‘service-registry’ contains invalid characters, please migrate to a valid format.
2020-02-24 20:56:49.437 INFO 18925 — [ main] o.s.cloud.context.scope.GenericScope : BeanFactory id=75b0a249-7c97-3cd0-97fc-f8f4f391c8b2
2020-02-24 20:56:49.782 INFO 18925 — [ 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-24 20:56:50.070 INFO 18925 — [ main] trationDelegate$BeanPostProcessorChecker : Bean ‘org.springframework.cloud.autoconfigure.ConfigurationPropertiesRebinderAutoConfiguration’ of type [org.springframework.cloud.autoconfigure.ConfigurationPropertiesRebinderAutoConfiguration$$EnhancerBySpringCGLIB$$a84cc90f] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2020-02-24 20:56:50.379 INFO 18925 — [ main] o.s.b.w.embedded.tomcat.TomcatWebServer : Tomcat initialized with port(s): 8787 (http)
2020-02-24 20:56:50.398 INFO 18925 — [ main] o.apache.catalina.core.StandardService : Starting service [Tomcat]
2020-02-24 20:56:50.398 INFO 18925 — [ main] org.apache.catalina.core.StandardEngine : Starting Servlet engine: [Apache Tomcat/9.0.27]
2020-02-24 20:56:50.471 INFO 18925 — [ main] o.a.c.c.C.[Tomcat].[localhost].[/] : Initializing Spring embedded WebApplicationContext
2020-02-24 20:56:50.472 INFO 18925 — [ main] o.s.web.context.ContextLoader : Root WebApplicationContext: initialization completed in 2419 ms
2020-02-24 20:56:50.526 INFO 18925 — [ main] .c.b.s.b.s.r.CamundaJerseyResourceConfig : Configuring camunda rest api.
2020-02-24 20:56:50.552 INFO 18925 — [ main] .c.b.s.b.s.r.CamundaJerseyResourceConfig : Finished configuring camunda rest api.
2020-02-24 20:56:50.806 WARN 18925 — [ main] c.n.c.sources.URLConfigurationSource : No URLs will be polled as dynamic configuration sources.
2020-02-24 20:56:50.806 INFO 18925 — [ main] c.n.c.sources.URLConfigurationSource : To enable URLs as dynamic configuration sources, define System property archaius.configurationSource.additionalUrls or make config.properties available on classpath.
2020-02-24 20:56:50.827 INFO 18925 — [ main] c.netflix.config.DynamicPropertyFactory : DynamicPropertyFactory is initialized with configuration sources: com.netflix.config.ConcurrentCompositeConfiguration@2e71240b
2020-02-24 20:56:50.949 INFO 18925 — [ main] c.a.d.s.b.a.DruidDataSourceAutoConfigure : Init DruidDataSource
2020-02-24 20:56:51.221 INFO 18925 — [ main] com.alibaba.druid.pool.DruidDataSource : {dataSource-1} inited
2020-02-24 20:56:51.538 INFO 18925 — [ main] o.hibernate.jpa.internal.util.LogHelper : HHH000204: Processing PersistenceUnitInfo [name: default]
2020-02-24 20:56:51.628 INFO 18925 — [ main] org.hibernate.Version : HHH000412: Hibernate Core {5.4.8.Final}
2020-02-24 20:56:51.780 INFO 18925 — [ main] o.hibernate.annotations.common.Version : HCANN000001: Hibernate Commons Annotations {5.1.0.Final}
2020-02-24 20:56:51.917 INFO 18925 — [ main] org.hibernate.dialect.Dialect : HHH000400: Using dialect: org.hibernate.dialect.PostgreSQL10Dialect
2020-02-24 20:56:52.178 INFO 18925 — [ main] o.h.e.t.j.p.i.JtaPlatformInitiator : HHH000490: Using JtaPlatform implementation: [org.hibernate.engine.transaction.jta.platform.internal.NoJtaPlatform]
2020-02-24 20:56:52.186 INFO 18925 — [ main] j.LocalContainerEntityManagerFactoryBean : Initialized JPA EntityManagerFactory for persistence unit ‘default’
2020-02-24 20:56:52.225 INFO 18925 — [ main] org.camunda.bpm.spring.boot : STARTER-SB040 Setting up jobExecutor with corePoolSize=3, maxPoolSize:10
2020-02-24 20:56:52.227 INFO 18925 — [ main] o.s.s.concurrent.ThreadPoolTaskExecutor : Initializing ExecutorService ‘camundaTaskExecutor’
2020-02-24 20:56:52.337 INFO 18925 — [ main] org.camunda.bpm.engine.cfg : ENGINE-12003 Plugin ‘CompositeProcessEnginePlugin[genericPropertiesConfiguration, camundaProcessEngineConfiguration, camundaDatasourceConfiguration, camundaJpaConfiguration, camundaJobConfiguration, camundaHistoryConfiguration, camundaMetricsConfiguration, camundaAuthorizationConfiguration, CreateAdminUserConfiguration[adminUser=AdminUserProperty[id=kermit, firstName=Kermit, lastName=Kermit, email=kermit@localhost, password=******]], failedJobConfiguration, CreateFilterConfiguration[filterName=All tasks], disableDeploymentResourcePattern, eventPublisherPlugin]’ activated on process engine ‘default’
2020-02-24 20:56:52.341 INFO 18925 — [ main] org.camunda.bpm.spring.boot : STARTER-SB020 ProcessApplication enabled: autoDeployment via springConfiguration#deploymentResourcePattern is disabled
2020-02-24 20:56:52.342 INFO 18925 — [ main] o.c.b.s.b.s.event.EventPublisherPlugin : EVENTING-001: Initialized Camunda Spring Boot Eventing Engine Plugin.
2020-02-24 20:56:52.343 INFO 18925 — [ main] o.c.b.s.b.s.event.EventPublisherPlugin : EVENTING-003: Task events will be published as Spring Events.
2020-02-24 20:56:52.343 INFO 18925 — [ main] o.c.b.s.b.s.event.EventPublisherPlugin : EVENTING-005: Execution events will be published as Spring Events.
2020-02-24 20:56:52.346 INFO 18925 — [ main] o.c.b.s.b.s.event.EventPublisherPlugin : EVENTING-007: History events will be published as Spring events.
2020-02-24 20:56:55.209 INFO 18925 — [ main] org.camunda.bpm.engine : ENGINE-00001 Process Engine default created.
2020-02-24 20:56:55.269 INFO 18925 — [ main] org.camunda.bpm.spring.boot : STARTER-SB011 skip creating initial Admin User, user does exist: UserEntity[id=kermit, revision=3, firstName=Kermit, lastName=Kermit, email=kermit@localhost, password={SHA-512}F64mHEEDCHzBOEAuuHfC94/BRcH02kauYzkueucNwOQQPvxq3XyeOch3xCTcMaIWEFwAwcBMVESlUVUPAYNRdg==, salt=8VhNa02h+Kb7EbQmvIm6yA==, lockExpirationTime=null, attempts=0]
2020-02-24 20:56:55.749 WARN 18925 — [ 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-24 20:56:55.820 WARN 18925 — [ main] c.n.c.sources.URLConfigurationSource : No URLs will be polled as dynamic configuration sources.
2020-02-24 20:56:55.820 INFO 18925 — [ main] c.n.c.sources.URLConfigurationSource : To enable URLs as dynamic configuration sources, define System property archaius.configurationSource.additionalUrls or make config.properties available on classpath.
2020-02-24 20:56:56.147 INFO 18925 — [ main] o.c.b.s.b.s.w.f.LazyInitRegistration : lazy initialized org.camunda.bpm.spring.boot.starter.webapp.filter.LazySecurityFilter@1ef5cde4
2020-02-24 20:56:56.148 INFO 18925 — [ main] o.c.b.s.b.s.w.f.LazyInitRegistration : lazy initialized org.camunda.bpm.spring.boot.starter.webapp.filter.LazyProcessEnginesFilter@20e48e63
2020-02-24 20:56:56.382 WARN 18925 — [ main] ockingLoadBalancerClientRibbonWarnLogger : You already have RibbonLoadBalancerClient on your classpath. It will be used by default. As Spring Cloud Ribbon is in maintenance mode. We recommend switching to BlockingLoadBalancerClient instead. In order to use it, set the value of spring.cloud.loadbalancer.ribbon.enabled to false or remove spring-cloud-starter-netflix-ribbon from your project.
2020-02-24 20:56:56.467 INFO 18925 — [ main] o.s.b.a.e.web.EndpointLinksResolver : Exposing 2 endpoint(s) beneath base path ‘/actuator’
2020-02-24 20:56:56.557 INFO 18925 — [ main] o.s.c.n.eureka.InstanceInfoFactory : Setting initial instance status as: STARTING
2020-02-24 20:56:56.650 INFO 18925 — [ main] com.netflix.discovery.DiscoveryClient : Initializing Eureka in region us-east-1
2020-02-24 20:56:56.905 INFO 18925 — [ main] c.n.d.provider.DiscoveryJerseyProvider : Using JSON encoding codec LegacyJacksonJson
2020-02-24 20:56:56.906 INFO 18925 — [ main] c.n.d.provider.DiscoveryJerseyProvider : Using JSON decoding codec LegacyJacksonJson
2020-02-24 20:56:57.078 INFO 18925 — [ main] c.n.d.provider.DiscoveryJerseyProvider : Using XML encoding codec XStreamXml
2020-02-24 20:56:57.078 INFO 18925 — [ main] c.n.d.provider.DiscoveryJerseyProvider : Using XML decoding codec XStreamXml
2020-02-24 20:56:57.302 INFO 18925 — [ main] c.n.d.s.r.aws.ConfigClusterResolver : Resolving eureka endpoints via configuration
2020-02-24 20:56:57.340 INFO 18925 — [ main] com.netflix.discovery.DiscoveryClient : Disable delta property : false
2020-02-24 20:56:57.340 INFO 18925 — [ main] com.netflix.discovery.DiscoveryClient : Single vip registry refresh property : null
2020-02-24 20:56:57.340 INFO 18925 — [ main] com.netflix.discovery.DiscoveryClient : Force full registry fetch : false
2020-02-24 20:56:57.340 INFO 18925 — [ main] com.netflix.discovery.DiscoveryClient : Application is null : false
2020-02-24 20:56:57.341 INFO 18925 — [ main] com.netflix.discovery.DiscoveryClient : Registered Applications size is zero : true
2020-02-24 20:56:57.341 INFO 18925 — [ main] com.netflix.discovery.DiscoveryClient : Application version is -1: true
2020-02-24 20:56:57.341 INFO 18925 — [ main] com.netflix.discovery.DiscoveryClient : Getting all instance registry info from the eureka server
2020-02-24 20:56:57.515 INFO 18925 — [ main] com.netflix.discovery.DiscoveryClient : The response status is 200
2020-02-24 20:56:57.518 INFO 18925 — [ main] com.netflix.discovery.DiscoveryClient : Starting heartbeat executor: renew interval is: 5
2020-02-24 20:56:57.521 INFO 18925 — [ main] c.n.discovery.InstanceInfoReplicator : InstanceInfoReplicator onDemand update allowed rate per min is 4
2020-02-24 20:56:57.530 INFO 18925 — [ main] com.netflix.discovery.DiscoveryClient : Discovery Client initialized at timestamp 1582549017528 with initial instances count: 0
2020-02-24 20:56:57.536 INFO 18925 — [ main] o.s.c.n.e.s.EurekaServiceRegistry : Registering application CAMUNDA-SERVICE with eureka with status UP
2020-02-24 20:56:57.537 INFO 18925 — [ main] com.netflix.discovery.DiscoveryClient : Saw local status change event StatusChangeEvent [timestamp=1582549017537, current=UP, previous=STARTING]
2020-02-24 20:56:57.540 INFO 18925 — [nfoReplicator-0] com.netflix.discovery.DiscoveryClient : DiscoveryClient_CAMUNDA-SERVICE/192.168.4.207:camunda-service:8787: registering service…
2020-02-24 20:56:57.602 INFO 18925 — [ main] org.camunda.bpm.container : ENGINE-08024 Found processes.xml file at file:/media/user/_dde_data/vscode_projects/crusoefo/camunda-centre/target/classes/META-INF/processes.xml
2020-02-24 20:56:57.605 INFO 18925 — [ main] org.camunda.bpm.container : ENGINE-08025 Detected empty processes.xml file, using default values
2020-02-24 20:56:57.618 INFO 18925 — [ main] org.camunda.bpm.container : ENGINE-08023 Deployment summary for process archive ‘app’:
2step.bpmn
2020-02-24 20:56:57.620 INFO 18925 — [nfoReplicator-0] com.netflix.discovery.DiscoveryClient : DiscoveryClient_CAMUNDA-SERVICE/192.168.4.207:camunda-service:8787 - registration status: 204
2020-02-24 20:56:57.667 INFO 18925 — [ main] org.camunda.bpm.application : ENGINE-07021 ProcessApplication ‘app’ registered for DB deployments [26a451c8-5704-11ea-a565-a68449c5dc0b]. Will execute process definitions
AndOneTwoSteps[version: 1, id: AndOneTwoSteps:1:26c1018a-5704-11ea-a565-a68449c5dc0b]
Deployment does not provide any case definitions.
2020-02-24 20:56:57.677 INFO 18925 — [ main] org.camunda.bpm.container : ENGINE-08050 Process application app successfully deployed
2020-02-24 20:56:57.714 INFO 18925 — [ main] o.s.b.w.embedded.tomcat.TomcatWebServer : Tomcat started on port(s): 8787 (http) with context path ‘’
2020-02-24 20:56:57.715 INFO 18925 — [ main] .s.c.n.e.s.EurekaAutoServiceRegistration : Updating port to 8787
2020-02-24 20:56:57.720 INFO 18925 — [ main] com.crusoe.fo.App : Started App in 10.792 seconds (JVM running for 11.164)
2020-02-24 20:56:57.730 INFO 18925 — [ main] org.camunda.bpm.engine.jobexecutor : ENGINE-14014 Starting up the JobExecutor[org.camunda.bpm.engine.spring.components.jobexecutor.SpringJobExecutor].
2020-02-24 20:56:57.733 INFO 18925 — [ingJobExecutor]] org.camunda.bpm.engine.jobexecutor : ENGINE-14018 JobExecutor[org.camunda.bpm.engine.spring.components.jobexecutor.SpringJobExecutor] starting to acquire jobs
2020-02-24 20:57:27.518 INFO 18925 — [freshExecutor-0] com.netflix.discovery.DiscoveryClient : Disable delta property : false
2020-02-24 20:57:27.518 INFO 18925 — [freshExecutor-0] com.netflix.discovery.DiscoveryClient : Single vip registry refresh property : null
2020-02-24 20:57:27.518 INFO 18925 — [freshExecutor-0] com.netflix.discovery.DiscoveryClient : Force full registry fetch : false
2020-02-24 20:57:27.518 INFO 18925 — [freshExecutor-0] com.netflix.discovery.DiscoveryClient : Application is null : false
2020-02-24 20:57:27.518 INFO 18925 — [freshExecutor-0] com.netflix.discovery.DiscoveryClient : Registered Applications size is zero : true
2020-02-24 20:57:27.518 INFO 18925 — [freshExecutor-0] com.netflix.discovery.DiscoveryClient : Application version is -1: false
2020-02-24 20:57:27.518 INFO 18925 — [freshExecutor-0] com.netflix.discovery.DiscoveryClient : Getting all instance registry info from the eureka server
2020-02-24 20:57:27.542 INFO 18925 — [freshExecutor-0] com.netflix.discovery.DiscoveryClient : The response status is 200
I use vscode to run this project.It seems all OK.
I found out because of using JDK8.By switching to JDK13 all is OK.