Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WIP FUSETOOLS2-1624 - Support automatic restart #93

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

apupier
Copy link
Member

@apupier apupier commented May 10, 2022

When Automatic restart of Camel route is configured, the JMX connection
vanishes for few seconds. Adding code to be able to reconnect. As a
first iteration ,allow 5 seconds for the connection to be up again.

  • how to test it?
  • How to check we have no potential zombies if reconnection last more
    than 5 seconds or if it was an abrupt stop?

automaticReconnectionOnLiveReload

@apupier apupier force-pushed the 1624-supportAutomaticRedeploy branch from 443ea53 to 160b064 Compare May 10, 2022 14:57
When Automatic restart of Camel route is configured, the JMX connection
vanishes for few seconds. Adding code to be able to reconnect. As a
first iteration ,allow 5 seconds for the connection to be up again.

- how to test it?
- How to check we have no potential zombies if reconnection last more
than 5 seconds or if it was an abrupt stop?
- if automatic reload is done in the one second time between two check
of suspended nodes, we won't detect the reload. For now, I do not see a
better way than to live with it as it shouldn't occur a lot, with a very
simple use case, it is taking always more than a second on my relatively
fast machine.

Current proposal is working only with Quarkus with a not robust
implementation and I cannot manage to write a test for this case.

i tis not working with Camel JBangand I do not see how to detect that
there was a reload. I'm wondering if the breakpoints are kept on route
reload, it would not be enough to work on most cases.

Maybe a better approach is to support the "restart" of the debug adapter
which is available in VS Code UI when the code has been detected as
modified.

Signed-off-by: Aurélien Pupier <[email protected]>
@apupier apupier force-pushed the 1624-supportAutomaticRedeploy branch from 160b064 to 233a05c Compare May 11, 2022 14:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant