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 have been used this lib, but after a while the connection auto close and when start it again it connect with another consumer in queue,
I can publish in another queues but it stop consuming. in order to finger out what is happen the solution is complete delete the queue and restart it again. I read in pub.dev that the driver does not currently support recovering client topologies when re-establishing connections. This feature may be implemented in a future version.
is that what is happening ?
how can I try implement this an check is there is an stable connection or if the queue has consumers?
how can I persist the consumer to avoid this?
thanks
This behavior is intentional as per the comment about not re-establishing topologies after re-connecting.
The client will surface connection lost errors via a broadcast stream that you can subscribe to.
The recommended approach is to specify an error listener and check for connection-lost errors:
client.errorListener((ex) =>handleError(ex));
voidhandleError(Exception ex) {
// Check if ex is a ConnectionException or it's message contains "Lost connection to server"// and recreate topology.
}
I have been used this lib, but after a while the connection auto close and when start it again it connect with another consumer in queue,
I can publish in another queues but it stop consuming. in order to finger out what is happen the solution is complete delete the queue and restart it again. I read in pub.dev that
the driver does not currently support recovering client topologies when re-establishing connections. This feature may be implemented in a future version.
is that what is happening ?
how can I try implement this an check is there is an stable connection or if the queue has consumers?
how can I persist the consumer to avoid this?
thanks
The text was updated successfully, but these errors were encountered: