I’m using a Deployment to deploy JBPM in Kubernetes, but when the Deployment’s replicas count is set to 2, although the second pod’s status shows as running, there are ERRORS in the logs.
[Error log shows:]

I’m using a Deployment to deploy JBPM in Kubernetes, but when the Deployment’s replicas count is set to 2, although the second pod’s status shows as running, there are ERRORS in the logs.
[Error log shows:]

I’m using a Deployment to deploy JBPM in Kubernetes, but when the Deployment’s replicas count is set to 2, although the second pod’s status shows as running, there are ERRORS in the logs.
[Error log shows:]

I have created the sample and facing the following error. Can anyone describe why this is happening? I am using jBPM Version 7.

I have created the sample and facing the following error. Can anyone describe why this is happening? I am using jBPM Version 7.

I have use case where I’m creating the process and after some time I’m staring the process with jbpm 5.5.
Once I create the process , jbpm will internally do insertion to few tables like SessionInfo,..etc.
The same way when I start the process , jbpm will internally do insertion to few tables like ProcessInstanceLog,..etc.

TaskService.suspend(id, user) is used for suspending tasks status by taking the inputs as Task Id and User Id in JBPM V6.4.
But we have some tasks in Created Status which are not being considered by suspend API to mark it as Suspended.
Only Ready and Reserved status is changed to Suspend.

I’m new with JBPM and I downloaded the latest Community version from official website.