-
Notifications
You must be signed in to change notification settings - Fork 17
Reconnect closed connection? #65
Comments
Thank you for your time. Team RabbitMQ uses GitHub issues for specific actionable items engineers can work on. This assumes we have a certain amount of information to work with. We get at least a dozen of questions through various venues every single day, often quite light on details. Getting all the details necessary to make a conclusion or even form a hypothesis about what's happening can take a fair amount of time. Please help others help you by providing as much relevant information as possible on the list:
Feel free to edit out hostnames and other potentially sensitive information. When/if we have enough details and evidence we'd be happy to file a new issue. Thanks you. |
The plugin uses a pool of connections and opens new ones as necessary. It also purges inactive connections because having a pool of constantly open ones is not always desired. Please provide more details on the mailing list, at the very minimum the server version used and log files. |
OK, I think I understand what the issue really is. |
The server version is RabbitMQ 3.6.9 installed from the Ubuntu APT repository. |
See #66. What happened in your case is:
It should not affect the entire pool of connections, however, but if it does, re-enabling the LDAP plugin or worst case restarting the node should help. We will rectify connection purging for 3.6.10. |
Yes, restarting the node helps. I will wait for 3.6.10, thanks! |
@lutzhorn thank you for providing enough information for us to investigate! |
Using this configuration
works fine. But after some time of inactivity(?), the connection to the LDAP server is closed, the next authentication attempt produces this error:
How can I configure the
rabbit_auth_backend_ldap
to keep the connection open or reconnect automatically?The text was updated successfully, but these errors were encountered: