I have an issue with the deployment from Modeler to a Spring Boot embedded Camunda process engine with enabled ReST API (v7.14). And it’s really strange - at least for me
When I set an explicit engine name in my application.properties (e.g. camunda.bpm.process-engine-name=aname), the deployment cease to work, because no running engine is found. With Wireshark I found out, that the /deployment endpoint is queried and indeed it returns that error:
curl "http://localhost:8080/engine-rest/deployment"
{"type":"InvalidRequestException","message":"No process engine available"}
When I remove the explicit name in the application.properties, everything is ok again:
That might be for the deployment per se, but this is the URL that Modeler calls, when I point the deployment dialog to http://localhost:8080/engine-rest. In case an explicit name is set I get this red triangle thing that there’s no running engine. If I remove the name and just use the default, Modeler is fine.
Sorry, I think we have a misunderstanding here. So for me it works generally when I only point it to /engine-rest (of course only when i leave the engine name alone as written).
In the screenshot you see the situation when I run my app without an engine name set. When I set an engine name, I have that red triangle next to the REST endpoint input (sorry, I’m only allowed to attach one media).
What the Modeler does internally to check if an engine is running (checked with Wireshark):
It does a GET on /engine-rest/deployment (so not the POST yet to deploy anything). When no name is set the response is [] with HTTP status 200, with a name it is {"type":"InvalidRequestException","message":"No process engine available"} with HTTP status 400. I guess this error makes the little red triangle appear.
I do not understand, why giving a name to the engine causes this invalid request exception.