According to rabbitmq documentation, the connection string allows a connection_timeout parameter. However, testing it, it doesn't seem honoured.
What works, instead is the timeout parameter of connect_robust().
This makes so that, in order to configure the timeout, it takes extra code: maybe to add a new configuration parameter to an app, maybe code to extract the timeout from the connection string.
Shouldn't the timeout in the connection string be honoured?
(note: in psycopg 3 we had a similar issue and had to handle the connection timeout manually, but we do take it from the connection info).
According to rabbitmq documentation, the connection string allows a
connection_timeoutparameter. However, testing it, it doesn't seem honoured.What works, instead is the
timeoutparameter ofconnect_robust().This makes so that, in order to configure the timeout, it takes extra code: maybe to add a new configuration parameter to an app, maybe code to extract the timeout from the connection string.
Shouldn't the timeout in the connection string be honoured?
(note: in psycopg 3 we had a similar issue and had to handle the connection timeout manually, but we do take it from the connection info).