I'm using Spring 4.2 websockets with stomp on the serverside. Client uses stomp.js. I noticed that it is possible for a user to subscribe the same topic-destination multiple times. When a message is delivered to this destination, the user receives it multiple times too.

Why is this possible? What would be a use case for this?

How can I avoid it? The @SubscribeMapping is called AFTER the subscription and I cannot cancel it

Spring, Stomp: How to avoid multiple subscriptions to same destination by same user

I am running on a spring-boot internet app with the use of web sockets and I have a practical implementation for a single server.

I'm researching the first-rate solution for integrating a cluster of servers so that the clients connected to each of the weight-balanced servers might get the broadcasted messages despatched from all servers.

What is the best practice to connect clustered web socket servers?

I see references to RabitMQ but on account that we've got is already in location, I'm looking to parent out if Redis will work as a stomp message dealer.

stomp

Trending Blogposts on stomp

Popular Discussions on stomp

openSpring, Stomp: How to avoid multiple subscriptions to same destination by same user

2

0

0

openSynching Stomp over Web Sockets in SpringBoot on a Cluster with Redis as a Message Broker

1

0

0

PRODUCTS

QUICK LINKS

LEGAL

stomp

Trending Blogposts on stomp

Popular Discussions on stomp

openSpring, Stomp: How to avoid multiple subscriptions to same destination by same user

2

0

0

openSynching Stomp over Web Sockets in SpringBoot on a Cluster with Redis as a Message Broker

1

0

0