Replies: 2 comments 6 replies
-
I can add that I managed to get an error message back now saying: 2024-05-13T10:44:29.233897Z DEBUG amq_proxy.server Client connection failure (192.168.160.119:62356) #<AMQProxy::Client::NegotiationError:Client negotiation failed> |
Beta Was this translation helpful? Give feedback.
3 replies
-
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi, the AMQProxy looks exactly what we are after. We are connecting to an external broker on the internet that runs RabbitMQ. Our Java application resides in a secure network zone that aren't allowed to connect directly to the broker on the internet. We are using Apache Qpid client library to connect to the broker using AMQPS.
We just installed the amqproxy as a service on a Debian server and it runs fine on port 5673. The upstream url is set to amqps://tb.test.nhn.no. (default port)
When I run our Java program locally I get the error message "Failed to connect to remote at: amqps://some.server.net:5673"
We create a JMS Connection Factory with a few parameters, like username and password that the upstream broker wants but we use the local url to amqproxy. Should this work or are we trying to do something impossible here?
Beta Was this translation helpful? Give feedback.
All reactions