Http Connector Hangs After Application Server Restart (Tomcat)

Hi,

I am looking for some support to debug and troubleshoot a problem we are facing with camunda. We are running camunda 7.8 within a tomcat 8 application server.

What we have found is that when tomcat has restarted and we kick off a BPMN process which has a Http Connector and a corresponding message receive task for async messaging is that the process stops at the http connector (Call Http URL in the screenshot) without any indication in the logs as to what is happening. When we look on the server where the Url is configured for the Http connector we can see that no http requests was even made to the server. It is as if the Http connector just stalls.

Strangely re-uploading the bpmn file which has the http connector and message receive tasks solves the issue and the next process ran continues fine.

Has anyone else perhaps seen this behaviour or know what could possibly cause it? Secondly which java packages can I add in the logging file to provide us with more details on what is going on?

I have attached a sample BPMN file which shows the connector setup we use. Any advise would be appreciated.

example.bpmn (9.2 KB)

@some-camunda-user this sounds like deploymentAware.

Hi @StephenOTT,

Thanks a lot for the reply and sorry for my late reply. I have made the changes to the config and disabled context aware. I have been testing this for about a month now and we haven’t had the issue occur again.

Regards