🎄 Happy Holidays! 🥳
Most of Solace is closed December 24–January 1 so our employees can spend time with their families. We will re-open Thursday, January 2, 2024. Please expect slower response times during this period and open a support ticket for anything needing immediate assistance.
Happy Holidays!
Please note: most of Solace is closed December 25–January 2, and will re-open Tuesday, January 3, 2023.
python qpid-proton cannot access solace broker after rename Message VPN
Ting_
Member Posts: 3 ✭
Hi everyone,
I have some problems with connecting to solace with qpid-proton python.
I connected to Solace that isn’t running on my local machine but other server, and I could send the message into the queue with the subscription topic and also receive the message from the queue successfully for a while.
All I specified was the ip, port(amqp service), and the topic or queue that I’m interested in in my qpid-proton python project.
However, after the message VPN is renamed, I couldn’t connect to it anymore. The rest of the configuration of the message VPN stayed the same as the original setup. The broker only has one message VPN. My original thought was like it should be fine for renaming the VPN cause I don’t use it in my connection setting.
This is the url that my program tried to connect:
Url('amqp://<ip>:<port>/<queue_name>')
and I saw:
[ERROR] <_handlers on_transport_error 708> proton.pythonio: Connection refused to all addresses
[INFO] <_reactor on_transport_closed 1117> Disconnected will try to reconnect after 10.0 seconds
If only the VPN name changed, what would be the correct behavior toward my connection?
I also check if it’s the problem of firewall, but when I `nc -vz <ip> <port>`, it showed this information
Ncat : Version 7.70
Ncat: Connected to <ip>:<port>
Ncat: 0 bytes sent, 0 bytes received in 0.01 seconds.
so I don’t think firewall is the problem!
What do you suggest me to do to diagnose this problem?
I have some problems with connecting to solace with qpid-proton python.
I connected to Solace that isn’t running on my local machine but other server, and I could send the message into the queue with the subscription topic and also receive the message from the queue successfully for a while.
All I specified was the ip, port(amqp service), and the topic or queue that I’m interested in in my qpid-proton python project.
However, after the message VPN is renamed, I couldn’t connect to it anymore. The rest of the configuration of the message VPN stayed the same as the original setup. The broker only has one message VPN. My original thought was like it should be fine for renaming the VPN cause I don’t use it in my connection setting.
This is the url that my program tried to connect:
Url('amqp://<ip>:<port>/<queue_name>')
and I saw:
[ERROR] <_handlers on_transport_error 708> proton.pythonio: Connection refused to all addresses
[INFO] <_reactor on_transport_closed 1117> Disconnected will try to reconnect after 10.0 seconds
If only the VPN name changed, what would be the correct behavior toward my connection?
I also check if it’s the problem of firewall, but when I `nc -vz <ip> <port>`, it showed this information
Ncat : Version 7.70
Ncat: Connected to <ip>:<port>
Ncat: 0 bytes sent, 0 bytes received in 0.01 seconds.
so I don’t think firewall is the problem!
What do you suggest me to do to diagnose this problem?
0
Answers
-
AMQP doesn't have the concept of message VPN, so each VPN will have a different AMQP port. Did you change the port to the AMQP port for the new message VPN?
2 -
Hi amackenzie,
Thank you for your reply. It's good to be sure that AMQP doesn't have the concept of message VPN.
It seems like the whole problem resolved itself after restarting the application several times.
Thank you!0
