Environment (Required on creation):

Onboarding/Test

Description (Required on creation; please attach any relevant screenshots, stacktraces, log Camunda Process Service Won't Startfiles, etc. to the ticket):

Process Service Won't start

06-03-2021 11:49:49         INFO main o.c.spin: SPIN-01010 Discovered Spin data format provider: org.camunda.spin.impl.json.jackson.format.JacksonJsonDataFormatProvider[name = application/json]
06-03-2021 11:49:49         INFO main o.c.spin: SPIN-01009 Discovered Spin data format: org.camunda.spin.impl.json.jackson.format.JacksonJsonDataFormat[name = application/json]
06-03-2021 11:49:53         INFO main o.c.b.engine: ENGINE-00001 Process Engine default created.

It appears that it won't start due to a query that is timing out similar to this:
select B.*
from ACT_GE_BYTEARRAY B
inner join
(select B.NAME_, MAX(D.DEPLOY_TIME_) DEPLOY_TIME_
from ACT_GE_BYTEARRAY B
inner join ACT_RE_DEPLOYMENT D
on B.DEPLOYMENT_ID_ = D.ID_
where D.NAME_ = 'SpringAutoDeployment'
and (D.SOURCE_ is null or D.SOURCE_ = 'abc')
and B.NAME_ in ( 'radiology_prediction.bpmn' )
group by B.NAME_) LAST_RESOURCE
on B.NAME_ = LAST_RESOURCE.NAME_
inner join ACT_RE_DEPLOYMENT D
on B.DEPLOYMENT_ID_ = D.ID_
and D.DEPLOY_TIME_ = LAST_RESOURCE.DEPLOY_TIME_
and D.NAME_ = 'SpringAutoDeployment'
and (D.SOURCE_ is null or D.SOURCE_ = 'abc')
and D.TENANT_ID_ is null
order by B.ID_ asc
 

The Precise Query
44
05-11-2021 13:39:24 DEBUG restartedMain c.c.p.ProcessServiceConfig: post build
05-11-2021 13:39:24 DEBUG restartedMain o.c.b.e.i.p.e.P.lockDeploymentLockProperty: ==> Preparing: SELECT VALUE_ FROM ACT_GE_PROPERTY WHERE NAME_ = 'deployment.lock' for update
05-11-2021 13:39:24 DEBUG restartedMain o.c.b.e.i.p.e.P.lockDeploymentLockProperty: ==> Parameters:
05-11-2021 13:39:24 DEBUG restartedMain o.c.b.e.i.p.e.P.lockDeploymentLockProperty: <== Total: 1
05-11-2021 13:39:24 DEBUG restartedMain o.c.b.e.i.p.e.R.selectLatestResourcesByDeploymentName_postgres: ==> Preparing: select B.* from ACT_GE_BYTEARRAY B inner join (select B.NAME_, MAX(D.DEPLOY_TIME_) DEPLOY_TIME_ from ACT_GE_BYTEARRAY B inner join ACT_RE_DEPLOYMENT D on B.DEPLOYMENT_ID_ = D.ID_ where D.NAME_ = ? and (D.SOURCE_ is null or D.SOURCE_ = ? ) and B.NAME_ in ( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ) group by B.NAME_) LAST_RESOURCE on B.NAME_ = LAST_RESOURCE.NAME_ inner join ACT_RE_DEPLOYMENT D on B.DEPLOYMENT_ID_ = D.ID_ and D.DEPLOY_TIME_ = LAST_RESOURCE.DEPLOY_TIME_ and D.NAME_ = ? and (D.SOURCE_ is null or D.SOURCE_ = ? ) and D.TENANT_ID_ is null order by B.ID_ asc
 

We also saw a failure to run Automatic Vacuum Analyze this morning. Not sure if it is related.

We are running a Vaccuum Analyze on the table ACT_GE_BYTEARRAY now, as that seemed to work the last time this happened.

Is there anything we can do to prevent this?
 
 

Steps to reproduce (Required on creation):

Observed Behavior (Required on creation):

Service won't start

Expected behavior (Required on creation):

Service to start

Root Cause (Required on prioritization):

Solution Ideas (Optional):

Hints (Optional):