Questions tagged [jms-topic]

A distribution mechanism for publishing messages that are delivered to multiple subscribers.

The use case for JMS Topic includes these considerations:

  1. A distribution mechanism for publishing messages that are delivered to multiple subscribers.
  2. Multiple consumers require delivery of the message.
  3. There is a timing dependency between publishers and subscribers. The publisher must create a subscription in order for clients to be able to subscribe. The subscriber must remain continuously active to receive messages, unless it has established a durable subscription. In that case, messages published while the subscriber is not connected will be redistributed whenever it reconnects.
300 questions
0
votes
1 answer

Consume message only once from Topic per listeners running in cluster

I'm implementing an Domain Event infrastructure, but the project doesn't allow any messaging infra(financial services client) so found an alternative in Hazelcast Topics and ExecutorService, But the problem is when running in cluster the message…
Somasundaram Sekar
  • 5,244
  • 6
  • 43
  • 85
0
votes
0 answers

Topic not able to receive message

I have a non durable Topic client which is supposed to receive messages asynchronously using a listener. When message is published on Topic, i can see on admin console that message is published and consumed but my client never receives it. Client…
Lokesh
  • 7,810
  • 6
  • 48
  • 78
0
votes
1 answer

If my producer producing, then why the consumer couldn't consume? it stuck @ poll()

Im publishing to the remote kafka server and try to consume messages from that remote server. (Kafka v 0.90.1) Publishing works fine but nor the consuming. Publisher package org.test; import java.io.IOException; import java.util.Properties; import…
Ratha
  • 9,434
  • 17
  • 85
  • 163
0
votes
1 answer

How to know when connection to a JMS Topic is lost?

I have a Java rich client application that registers a durable subscription on a remote HornetQ JMS Topic on startup. However if the server restarts the connection is lost and can only be restored by restarting the client application. This leads to…
Florian Genser
  • 160
  • 2
  • 7
0
votes
0 answers

Root exception is java.rmi.ConnectIOException: non-JRMP server at remote endpoint

I'm trying to read JMS queue from a server, I am able to ping the IP and port from my machine but when I execute my queue program it throws the below error any help would be appreciated. public class QueueReceive implements MessageListener { public…
0
votes
1 answer

REST Service waiting on a Response of asynchronous processes

Have a REST Service developed using Spring Boot The API currently uses JMS to publish to a Topic & the topic has multiple subscribers. Now, we have a process "X", which consolidates the response of these topics and pushes the response to a…
Narendra N
  • 1,270
  • 1
  • 9
  • 14
0
votes
1 answer

JMS - Using Topics on WebSphere Application Server 7

I have a sender and a receiver for a particular Topic. I'm running the sender and receiver as servlets on WAS 7.0. The Topic and Topic Connection Factory is being setup on WAS. But I'm not able to receive the message that is send. It works fine when…
Apps
  • 3,284
  • 8
  • 48
  • 75
0
votes
1 answer

How are subscribers maintained in case of topic based distributed messaging

I have following two questions related to distributed messaging system. How is topic different from Queue? How are subscribers maintained in case of topics. Please share any document or link which can be helpful to understand these…
Ashwani K
  • 7,880
  • 19
  • 63
  • 102
0
votes
2 answers

topic subscriber behaviour during multiple messages on a topic for long running process

I have a topic and corresponding subscriber in the form of Spring DMLC. My questions is related to the following scenario : A message is published on a topic and the subscriber starts processing the message. If another message arrives on this topic…
user2599052
  • 1,056
  • 3
  • 12
  • 27
0
votes
1 answer

How to integrate jms topic to feed Storm spout

I have an ActiveMQ topic provider. I need to feed the data received from that topic into the Storm topic. is there any way to do it directly or should I create intermediate queue and feed topic data into the queue and then pull the data into the…
Akila
  • 187
  • 2
  • 9
0
votes
2 answers

Mule JMS Topic and ActiveMQ Configuration

I am using Mule ESB to design a process whereby one can post a message to a topic. Subscribers will listen to the topic and receive messages. Each subscriber will act on the messages differently. The goal here is to have the ability to post a…
rray
  • 470
  • 3
  • 10
  • 27
0
votes
1 answer

Maintain order of messages while forwarding messages between two ActiveMQ brokers

I have an ActiveMQ setup where a source broker living in one data center forwards all messages arriving on certain topics to a destination broker in another data center. The consumer application consumes messages only from the destination broker.…
Phani K
  • 1,133
  • 2
  • 11
  • 14
0
votes
1 answer

How do I make a JMS topic variable in Grails?

I have recently run into a problem with trying to make the topic of my JMS @Subscriber a variable based upon environment. Currently, I have in my config.groovy: environments { development { jms.foo.msg = "my.jms.topic.dev.1_0" } …
DONKEYSAURUS
  • 141
  • 1
  • 3
0
votes
1 answer

ActiveMQ Redelivery Police only for a Message Container

In this piece of code I'm trying to set up a redelivery police only only for the messages in a specific topic: RedeliveryPolicy redeliveryPolicy = new RedeliveryPolicy(); emailByFolioRedeliveryPolicy.setInitialRedeliveryDelay(5000); …
Perimosh
  • 2,304
  • 3
  • 20
  • 38
0
votes
1 answer

Synchronizing subscribers to JMS Topic in active/active mode (WebLogic)

We work with WebLogic server, consuming JMS messages from a Topic. We have several nodes, working in active/active subscriber mode, without shared states other than dB (Oracle). The problem is, we have a requirement that only one of the subscribers…
MetaHnet
  • 125
  • 2
  • 12