You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've deployed (with @p4lik4ri) a dockerized Orion-LD instance with TROE enabled (-troe) and the TimescaleDB properly configured. Then, we have created an entity of type Vehicle and a Subscription with an MQTT endpoint.
However, when we modify the distanceCollision attribute, the broker crashes without displaying any error message in the logs, the notification isn't sent (although we can check in the logs of the Mosquitto server that the broker has tried to connect to it) and the failure isn't registered in the Subscription (status, isActive ... attributes are not creates).
Finally, if we restart the broker without the TROE enabled, the notifications are properly sent to the MQTT topic. However, if we restart the broker with the TROE enabled again, the notifications sometimes are sent (and the broker doesn't crash) but without including the value of the distanceCollision attribute.
I've deployed (with @p4lik4ri) a dockerized Orion-LD instance with TROE enabled (
-troe
) and the TimescaleDB properly configured. Then, we have created an entity of typeVehicle
and a Subscription with an MQTT endpoint.However, when we modify the
distanceCollision
attribute, the broker crashes without displaying any error message in the logs, the notification isn't sent (although we can check in the logs of the Mosquitto server that the broker has tried to connect to it) and the failure isn't registered in the Subscription (status, isActive
... attributes are not creates).Finally, if we restart the broker without the TROE enabled, the notifications are properly sent to the MQTT topic. However, if we restart the broker with the TROE enabled again, the notifications sometimes are sent (and the broker doesn't crash) but without including the value of the
distanceCollision
attribute.The text was updated successfully, but these errors were encountered: