We should add io.projectreactor:reactor-tools to improve debugging experience on modern IDEs like Intellij IDEA.
Project Reactor comes with a separate Java Agent that instruments the code and adds debugging info without paying a cost for capturing the stacktrace on every operator call like it happens with tracebacks in Debug mode and thus without the runtime performance overhead; see https://projectreactor.io/docs/core/release/reference/#reactor-tools-debug.
This could be very useful in some situations.
From documentation, there seem to be three possible ways to attach the instrumentation code.
We should add
io.projectreactor:reactor-tools
to improve debugging experience on modern IDEs like Intellij IDEA.Project Reactor comes with a separate Java Agent that instruments the code and adds debugging info without paying a cost for capturing the stacktrace on every operator call like it happens with tracebacks in Debug mode and thus without the runtime performance overhead; see https://projectreactor.io/docs/core/release/reference/#reactor-tools-debug.
This could be very useful in some situations.
From documentation, there seem to be three possible ways to attach the instrumentation code.
Attaching it directly
org.carapaceproxy.launcher.ServerMain
(and maybe also inorg.carapaceproxy.launcher.ZooKeeperMainWrapper
)Running
ReactorDebugAgent
as a Java AgentWe could add
-javaagent reactor-tools.jar
to the VM options, by adding it to theJAVA_OPTS
environment variable insetenv.sh
file.Running
ReactorDebugAgent
at build timeWe could add it with the Byte Buddy Maven Plugin: