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

[Bug] Camel Route Debug doesn't change UI view after NodeBreakpoint timed out #303

Open
jsolovjo opened this issue May 25, 2023 · 8 comments
Labels
area/camel kind/bug Something isn't working kind/ux Issues relating to user experience
Milestone

Comments

@jsolovjo
Copy link
Contributor

How to reproduce:

  • Navigate to Camel
  • Select any enabled camel route
  • Open Debug tab
  • Set a breakpoint on a camel route node
  • After ~5 minutes you will see a message in the logs that NodeBreakpoint timed out and the exchange is continued
2023-05-25 19:43:18.818  WARN 675 --- [eCamel_Worker-9] o.a.camel.impl.debugger.BacklogDebugger  : NodeBreakpoint at node setBody2 timed out and is continued exchangeId: 47A4D69A3A72C19-0000000000000008

However, the UI doesn't change - it shows a breakpoint on the camel route node
Screenshot 2023-05-25 at 19 44 21

@jsolovjo jsolovjo added kind/bug Something isn't working area/ui kind/ux Issues relating to user experience labels May 25, 2023
@tadayosi
Copy link
Member

Can anyone look at the issue? Maybe @phantomjinx ?

@tadayosi tadayosi added this to the 2024Q2 milestone Feb 5, 2024
@lhein lhein moved this from New to Backlog in Kanban Board Apr 25, 2024
@lhein lhein moved this from Backlog to Todo in Kanban Board Apr 25, 2024
@tadayosi tadayosi modified the milestones: 2024Q2, 2024Q3 Jul 17, 2024
@tadayosi tadayosi modified the milestones: 2024Q3, 2024Q4 Oct 8, 2024
@mmelko mmelko self-assigned this Oct 18, 2024
mmelko added a commit to mmelko/hawtio-next that referenced this issue Oct 22, 2024
mmelko added a commit to mmelko/hawtio-next that referenced this issue Oct 23, 2024
@mmelko
Copy link
Collaborator

mmelko commented Oct 23, 2024

Just wondering if the message doesn't mean that the exchange is released not the breakpoint removed.

@tadayosi tadayosi modified the milestones: 2024Q4, 2025Q1 Jan 8, 2025
@abkieling
Copy link

@jsolovjo Could you please verify this issue is fixed?

@jsolovjo
Copy link
Contributor Author

Hi @abkieling
I checked it and it seems it still has the same behaviour.
However, I am not sure whether it can be considered as a bug or not. As Matej mentioned the message says that the exchange is released not the breakpoint removed.

Image

@tadayosi
Copy link
Member

Then that's something that the assignee can investigate and confirm whether it's a bug or not.

@abkieling
Copy link

@oscerd What do you think Hawtio should do when a node breakpoint times out?

@abkieling abkieling moved this from In Progress to Todo in Kanban Board Feb 14, 2025
@abkieling
Copy link

@davsclaus What do you think Hawtio should do when a node breakpoint times out?

@davsclaus
Copy link
Member

Yeah there is some old state that needs to be removed on timeout
https://issues.apache.org/jira/browse/CAMEL-21747

The intention of the timeout is that its more of a safety so Camel does not block forever. The user is supposed to not be that slow before clicking next button.

@abkieling abkieling moved this from Todo to Blocked in Kanban Board Feb 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/camel kind/bug Something isn't working kind/ux Issues relating to user experience
Projects
Status: Blocked
Development

No branches or pull requests

5 participants