messagebroker

How to configure embedded ActiveMQ Broker URL with Spring Boot

对着背影说爱祢 提交于 2019-12-04 03:16:10
I followed a simple example of setting up and running embedded ActiveMQ with Spring Boot (version 1.4.X). Here's link to the example https://spring.io/guides/gs/messaging-jms/ My class is structured as below: @SpringBootApplication @EnableJms public class Application { @Autowired ConfigurableApplicationContext context; @Bean JmsListenerContainerFactory<?> myJmsContainerFactory(ConnectionFactory connectionFactory) { SimpleJmsListenerContainerFactory factory = new SimpleJmsListenerContainerFactory(); factory.setConnectionFactory(connectionFactory); return factory; } @JmsListener(destination =

REST APIs and messaging

|▌冷眼眸甩不掉的悲伤 提交于 2019-12-04 00:45:56
I have a system that exposes a REST API with a rich set of CRUD endpoints to manage different resources. The REST API is used also by a front-end application that executes calls by using Ajax. I would like to make some of these calls asynchronous and add reliability. The obvious choice seems a message broker (ActiveMQ, RabbitMQ, etc...). Never used message brokers before and I am wondering if they can be "put in front of" the REST API without having to rewrite them. I do not want to access the REST API only through the messaging system: for some endpoints, a call must always be synchronous and

Message broker vs. MOM (Message-Oriented Middleware)

血红的双手。 提交于 2019-12-03 03:10:10
问题 I'm a little confused as to what the difference is between a message broker e.g. RabbitMQ and Message-orientated Middleware. I can't find much info apart from what's on Wikipedia. When searching MOM I find info on AMQP which states is a protocol for MOM.. what does this mean? What is MOM then? I also have read that RabbitMQ implements the AMPQ protocol.. so why does that make a RabbitMQ a messsage broker? Are a message broker and MOM the same thing? Hope some can unravel my confusion. thanks

Difference between queue manager and message broker

烂漫一生 提交于 2019-12-02 19:13:22
What is the difference between a Websphere Message Broker and a Queue Manager. I guess the queue manager puts messages in the queue, takes messages out of the queue, moves messages to backout queues etc. So what is the job of the broker? Does it sit between the publisher and the Queue Manager or between the consumer and the Queue Manager? Websphere MQ is a software which uses the AMQ(Asynchronous messaging protocol) . You can achieve asynchronous messaging between your applications via Websphere MQ, which will make your infrastructure loosely coupled(Applications can keep working even though

What's the purpose of Kafka's key/value pair-based messaging?

老子叫甜甜 提交于 2019-12-02 17:50:42
All of the examples of Kafka | producers show the ProducerRecord 's key/value pair as not only being the same type (all examples show <String,String> ), but the same value . For example: producer.send(new ProducerRecord<String, String>("someTopic", Integer.toString(i), Integer.toString(i))); But in the Kafka docs, I can't seem to find where the key/value concept (and its underlying purpose/utility) is explained. In traditional messaging (ActiveMQ, RabbitMQ, etc.) I've always fired a message at a particular topic/queue/exchange. But Kafka is the first broker that seems to require key/value

Message broker vs. MOM (Message-Oriented Middleware)

泄露秘密 提交于 2019-12-02 16:40:15
I'm a little confused as to what the difference is between a message broker e.g. RabbitMQ and Message-orientated Middleware. I can't find much info apart from what's on Wikipedia. When searching MOM I find info on AMQP which states is a protocol for MOM.. what does this mean? What is MOM then? I also have read that RabbitMQ implements the AMPQ protocol.. so why does that make a RabbitMQ a messsage broker? Are a message broker and MOM the same thing? Hope some can unravel my confusion. thanks An overview - A protocol - A set of rules. AMQP - AMQP is an open internet protocol for reliably

With the clear session flag set to FALSE, I am missing the published values

亡梦爱人 提交于 2019-12-01 14:12:35
Is anyone has a logical explanation why despite I have the clear session flage = false I do not receive the updated published message I am subscribed to while i am not connected to the broker? With the aorementioned flag set to false I ran my App, And i kept publishing to a topic some values (from the PC to the broker not from the Android device to the broker). And then I unpluged the usb of the Android Device frm the pc, and kept publishing some values again. When I plugged the usb to the pc again, i expected to see the values I recently published to that topic, but I did not receive any. The

With the clear session flag set to FALSE, I am missing the published values

感情迁移 提交于 2019-12-01 12:10:42
问题 Is anyone has a logical explanation why despite I have the clear session flage = false I do not receive the updated published message I am subscribed to while i am not connected to the broker? With the aorementioned flag set to false I ran my App, And i kept publishing to a topic some values (from the PC to the broker not from the Android device to the broker). And then I unpluged the usb of the Android Device frm the pc, and kept publishing some values again. When I plugged the usb to the pc

How to resolve WebSphere MQ Reason code 2195 related error?

点点圈 提交于 2019-11-29 02:03:11
I am getting an WebSphere MQ Reason code 2195 MQRC_UNEXPECTED_ERROR when I try to connect to the message flows deployed on the execution group. Can somebody please tell me what exactly does this reason code mean? Queue manager, broker , execution group.. everything is up and running and the ports are also open. I am not getting anything worthwhile on the net. Please advise. The 2195 return code is a high-level exception that is hit when errors are not caught at lower levels in the code. Very often these are generated when some external dependency such as file access or Os resources does not

Does Spring @SubscribeMapping really subscribe the client to some topic?

爱⌒轻易说出口 提交于 2019-11-28 16:22:47
I am using Spring Websocket with STOMP, Simple Message Broker. In my @Controller I use method-level @SubscribeMapping , which should subscribe the client to a topic so that the client would receive the messages of that topic afterwards. Let say, the client subscribes to the topic "chat" : stompClient.subscribe('/app/chat', ...); As the client subscribed to "/app/chat ", instead of "/topic/chat" , this subscription would go to the method which is mapped using @SubscribeMapping : @SubscribeMapping("/chat") public List getChatInit() { return Chat.getUsers(); } Here is what Spring ref. says: By