NebulOuS

[Predictor orchestrator] Unresponsive after loosing connection to message broker

Bug #2066250 reported by Robert Sanfeliu
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
NebulOuS
New
High
Jan Marchel

Bug Description

After predictor orchestrator looses connection to NebulOuS message broker (and reconnects according to the logs), the component will not receive any new deployment application messages and won't be functional.

2024-05-20T11:14:41.966Z INFO 1 --- [:1): I/O Thread] o.a.q.p.client.impl.ClientConnection : Connection ID:07be7036-849a-4fb9-b11d-ecf65f1f5e7a:1:1 interrupted to server: nebulous-activemq:5672
2024-05-20T11:14:42.296Z INFO 1 --- [:1): I/O Thread] o.a.q.p.client.impl.ClientConnection : Connection ID:07be7036-849a-4fb9-b11d-ecf65f1f5e7a:1:1 reconnected to server: nebulous-activemq:5672

Robert Sanfeliu (rsprat)
Changed in nebulous:
assignee: Jan Floor (jan) → nobody
assignee: nobody → Jan Marchel (janmarchel7bulls)
Joanna Chmielewska (joannach)
Changed in nebulous:
importance: Undecided → High
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.