Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fails to Connect with non-Default exchanges #66

Open
randylcain opened this issue Apr 14, 2023 · 0 comments
Open

Fails to Connect with non-Default exchanges #66

randylcain opened this issue Apr 14, 2023 · 0 comments

Comments

@randylcain
Copy link

Running RabbitMQ 3.11.13 on Erlang 25.3 in Windows 10 Pro. RabbitMQ and Node-Red are both running on localhost.

Using topic exchange names like "KBL.727f89dc-431b-4577-9dba-9ab227f0a321" in VHosts named like "KBL" causes both amqp - in and amqp - out to remain disconnected while an ever-increasing number of connections are opened and maintained in RabbitMQ. Using the default topic exchange by leaving the field blank on the same VHost "KBL" does connect on both in and out.

It appears as if RMQ is accepting the connections as they are listed but the status of the node is "Disconnected". Two new connections appear every couple of seconds.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant