-
Task
-
Resolution: Won't Fix
-
L3 - Default
-
None
-
None
-
None
In order to ease-up the setup of debugging Camunda Run, we could add an explanation into the start scripts and/or documentation on how to achieve it.
What needs to be done?
- insert the following snippet before "-Dloader.path" in the start script:
-Xdebug -Xrunjdwp:server=y,transport=dt_socket,address=5050,suspend=y
- with "suspend" set to "y", the startup of Run will pause, waiting for a debugger to connect to the defined port (5050 in this case here)
- connect a debugger to localhost:5050 (e.g. by using an IDE and creating a remote debug application to that URL)
- debug
Optional:
- bake debugging into the start scripts as an optional parameter like "--debug" (maybe with a port and suspend yes/no?)