camel spring boot run configuration problems

[rastislavpapp]

• When running a 'normal' run configuration, IDEA changes the icon (to a X icon), giving the user feedback that it's trying to close it gracefully, and offering the user the possibility to kill it immediately with the X icon.
  • This seems to be the case for our spring boot run configuration as well, but the icon does not change. The functionality works though, the second press of the button kills the app
  • The first press of the stop button does not kill the app. When running via 'normal' Application run configuration, it does.
• debugging the app does work, but only our camel debugger works, the 'normal' debugging does not
• several times I've encountered a situation that after stopping the run configuration (or maybe the IDE itself) there remained a java process running, probably related to the debugger, and I've had to kill it to use the camel debugger again (there was a port conflict or something like that)-
• the camel debugger resumes the route when the breakpoint is toggled off

It's likely this applies to all the rest of the camel run configurations

[rastislavpapp]

• icon not changing - seems to be Intellij bug, does not work even with it's own run configurations
• first press not killing the app - it was because of graceful shutdown of route, when running via maven process, it just takes a bit longer (5 secs)

[rastislavpapp]

• java process running - probably my mistake, keeping the demo app running while restarting test ide instance

[rastislavpapp]

There's also a problem when running a spring boot app via standard Run Configuration (Application). The debugger does not attach properly, because of concurrency problem in org.apache.camel.main.DefaultConfigurationConfigurer#configureBacklogDebugger. The sequence of events is as follows:

1. the application starts, DefaultBacklogDebugger instance is created with suspendMode=true, because the camel idea plugin sets -Dorg.apache.camel.debugger.suspend=true, this gets picked up in org.apache.camel.impl.debugger.DefaultBacklogDebugger#resolveSuspendMode
2. the app is suspended
3. we're still in the DefaultConfigurationConfigurer#configureBacklogDebugger method, and now we get to debugger.setSuspendMode(config.isWaitForAttach()); // this option is named wait-for-attach
4. waitForAttach is false by default, so we set suspendMode=false in the debugger
5. NOW the debugger from idea plugin attaches, but since suspendMode=false, the suspend latch is not released; app is still suspended
6. app stays suspended forever

@davsclaus, I think I can fix this from the plugin side, but I think the problem is in the camel-debugger (or the spring boot component), because the suspendMode is read from 2 different places at once.

[davsclaus]

okay thanks, should the IDEA plugin perhaps set wait-for-attach=true as well in the command line ?

[rastislavpapp]

I've looked into that but I was unsure how to set that from a command line; the spring boot autoconfigurer sets the value based on a presence of a bean, it does not read it from properties (which I could override via -D parameter). As far I could tell.

[davsclaus]

Spring Boot should automatic read those values if they are part of auto-configuration