I'm behind a corporate HTTP proxy and want to send and receive messages to/from a ActiveMQ Artemis broker in the cloud.
On the broker Netty HTTP is activated and I'm able to send and receive messages using the Netty based ActiveMQ Artemis client on a computer without HTTP proxy.
I know that Netty HTTP client can be configured to use a HttpProxyHandler but I didn't find a way to configure this with the ActiveMQ Artemis client.
Any help is highly appreciated.
Related
We have an ActiveMQ server and our own API with WebSocket/STOMP service endpoint.
Is there a way to configure ActiveMQ to connect and subscribe to a topic in our API and then publish the messages in ActiveMQ?
If not, are there any other WebSocket/STOMP bridge components which could be used to achieve the same thing (subscribe to a topic in our API and post messages to a topic in ActiveMQ)?
The motivation of all this is... complicated.
ActiveMQ natively supports Camel routes. You could potentially use Camel's STOMP component to subscribe to your own STOMP endpoint and then send those messages to a local destination.
I have the following design:
Machine1
WebsocketApp
ActiveMQ broker
Machine2
WebsocketApp
ActiveMQ broker
Machine3
WebsocketApp
ActiveMQ broker
Machine4
WebsocketApp
ActiveMQ broker
The clients will use STOMP over WebSockets through an F5 load-balancer to connect to the ActiveMQ brokers. They can land on any machines based on the load factor.
For fail over scenarios how do we share the web socket sessions between ActiveMQ. Otherwise if the broker goes down all the sessions that it is holding will go down.
STOMP is a very simple protocol. It has no support for fail-over.
If the broker to which a STOMP client is connected goes down in your environment then that client's connection will go down and all the messages on that broker will be unavailable until the broker comes back up. The client will need to reconnect to another broker via the F5 URL.
STOMP connections are not like HTTP. They are stateful. Client "session" data is not shared among brokers. If a client's broker goes down then it cannot simply carry on as if nothing happened like is often possible for HTTP use-cases.
We have a use case to create websocket server. Mobile clients will connect to this websocket server. However mobile clients doesn't support stomp.
We would like to create a Java websocket server. spring does support websockets but it's heavily coupled with STOMP. we like to use Spring message broker concept here but because of Stomp, we are struck now. Is there anyway to overcome this and enable Spring websocket without STOMP but with Spring message broker concept?
I'm developing a service that sends messages to a RabbitMQ instance but the connectino has to be done through a proxy.
Is there a way to configure the connection so I can set up the host and port of the proxy as you can do when using RestTemplate but for RabbitTemplate?
Any help would be really appreciated,
Regards
I am trying to build a stomp websocket and use amazon activemq service.
it provides 2 url (one in case of failure) and I was wondering if I could use the ActiveMQConnectionFactory to setup the message broker.
so, basically inside DelegatingWebSocketMessageBrokerConfiguration use ActiveMQConnectionFactory to set the client on the stompBroker, instead of or along the ReactorNettyTcpClient.
Basicaly I want to take advantage of the failure recovery url in aws mq.