Is there a workaround to implement an activemq failover for stomp over websocket?
The uri in my web browser is ws://localhost:61614/stomp which is working fine. But adding failover:(ws://localhost:61614/stomp) will not work.
Appreciate any guidance.
Regards,
Walter
The failover transport only works with ActiveMQ's openwire based protocol. For stomp you need to handle all exceptions and reconnect when something goes wrong.
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.
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 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.
I am looking for creating a websocket client for using rabbit mq stomp over websocker using java.
I using jetty client and i am getting org.eclipse.jetty.websocket.api.UpgradeException: Didn't switch protocols
Looks like the issue is with the Rabbit MQ version. After I've upgraded from Ubuntu default one to the newest Rabbit MQ version from https://www.rabbitmq.com/install-debian.html it worked for me.
Look at this example: stomp-websockets-java-client
Please read first:
http://jmesnil.net/stomp-websocket/doc/
http://www.rabbitmq.com/blog/2012/05/14/introducing-rabbitmq-web-stomp/
not perfect, it's far from the worst way do messaging in the browser: exposing STOMP through Websockets.
http://activemq.apache.org/websockets.html says that these guys have implemented stomp over web sockets functionality. How is it different for the normal web sockets solution provided by Dojo's cometd? I thought web socket spec defines its own message structure and all? How does the HTTP upgraded web socket differs from this stomp over websockets? Would really appreciate some expert opinion guys.
Thanks,
Bhanu
The cometd implementation uses the Bayeux protocol, while the Apache implementation uses WebSockets.