下载地址:http://www.rabbitmq.com/download.html
下载:http://www.erlang.org/download/otp_win64_17.3.exe
rabbitmq-plugins enable rabbitmq_management
- 在浏览器中输入地址查看:http://127.0.0.1:15672/
wget http://packages.erlang-solutions.com/erlang-solutions-1.0-1.noarch.rpm
rpm -Uvh erlang-solutions-1.0-1.noarch.rpm
rpm --import http://packages.erlang-solutions.com/rpm/erlang_solutions.asc
上传rabbitmq-server-3.4.1-1.noarch.rpm文件到/usr/local/src/rabbitmq/
rpm -ivh rabbitmq-server-3.4.1-1.noarch.rpm
service rabbitmq-server restart
cp /usr/share/doc/rabbitmq-server-3.4.1/rabbitmq.config.example /etc/rabbitmq/
mv rabbitmq.config.example rabbitmq.config
vi /etc/rabbitmq/rabbitmq.config
rabbitmq-plugins enable rabbitmq_management
service rabbitmq-server restart
/sbin/iptables -I INPUT -p tcp --dport 15672 -j ACCEPT
/etc/rc.d/init.d/iptables save
可登陆管理控制台,可查看所有的信息,并且可以对用户,策略(policy)进行操作。
可登陆管理控制台,同时可以查看rabbitmq节点的相关信息(进程数,内存使用情况,磁盘使用情况等)
可登陆管理控制台, 同时可以对policy进行管理。但无法查看节点的相关信息(上图红框标识的部分)。
仅可登陆管理控制台,无法看到节点信息,也无法对策略进行管理。
输入:rabbitmq-plugins enable rabbitmq_management
首先在服务器上安装rabbitmq的服务,用docker拉取即可,不再详细描述。
<dependency> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-starter-amqp</artifactId></dependency>
spring.rabbitmq.host=192.168.0.86spring.rabbitmq.port=5672spring.rabbitmq.username=adminspring.rabbitmq.password=123456
P代表生产者,C代表消费者,红色代码消息队列。P将消息发送到消息队列,C对消息进行处理。
@Bean public Queue Queue() { return new Queue("hello"); }
@Controllerpublic class HelloSender { @Autowired private AmqpTemplate rabbitTemplate; public void send() { String context = "hello " + new Date(); System.out.println("Sender : " + context); this.rabbitTemplate.convertAndSend("hello", context); }}
@Component@RabbitListener(queues = "hello")public class HelloReceiver { @RabbitHandler public void process(String hello) { System.out.println("Receiver : " + hello); }}
@RunWith(SpringRunner.class)@SpringBootTestpublic class RabbitmqApplicationTests { @Autowired private HelloSender helloSender; @Test public void hello() throws Exception { helloSender.send(); }}
@Bean public Queue Queue2() { return new Queue("neo"); }
@Controllerpublic class NeoSender { @Autowired private AmqpTemplate rabbitTemplate; public void send(int i) { String context = "spirng boot neo queue"+" ****** "+i; System.out.println("Sender1 : " + context); this.rabbitTemplate.convertAndSend("neo", context); }}
1 @Component 2 @RabbitListener(queues = "neo") 3 public class NeoReceiver1 { 4 @RabbitHandler 5 public void process(String neo) { 6 System.out.println("Receiver 1: " + neo); 7 } 8 } 9 10 11 12 @Component13 @RabbitListener(queues = "neo")14 public class NeoReceiver2 {15 @RabbitHandler16 public void process(String neo) {17 System.out.println("Receiver 2: " + neo);18 }19 20 }
@Test public void oneToMany() throws Exception { for (int i=0;i<100;i++){ // Thread.sleep(10); neoSender.send(i); } }
通过这个例子我们可以看做高并发情况下的消息产生和消费,这会产生一个消息丢失的问题。万一客户端在处理消息的时候挂了,那这条消息就相当于被浪费了,针对这种情况,rabbitmq推出了消息ack机制,熟悉tcp三次握手的一定不会陌生。
很简单,在我们的配置类中,配置一个新的消费者,将原先的消费者先都去掉:
public SimpleMessageListenerContainer messageContainer() {
SimpleMessageListenerContainer container = new SimpleMessageListenerContainer(connectionFactory());
container.setExposeListenerChannel(true);
container.setMaxConcurrentConsumers(1);
container.setConcurrentConsumers(1);
container.setAcknowledgeMode(AcknowledgeMode.MANUAL);//消息确认后才能删除
container.setPrefetchCount(5);//每次处理5条消息
container.setMessageListener(new ChannelAwareMessageListener() {
public void onMessage(Message message, com.rabbitmq.client.Channel channel) throws Exception {
byte[] body = message.getBody();
System.out.println("消费端接收到消息 : " + new String(body));
channel.basicAck(message.getMessageProperties().getDeliveryTag(), false);
但这里会有个问题,test模式下消息发送完毕系统就会直接shutdown,所以只能消费部分消息,不过等真正启动项目,这个问题就不存在了。
生产者将消息不是直接发送到队列,而是发送到X交换机,然后由交换机发送给两个队列,两个消费者各自监听一个队列,来消费消息。
这种方式实现同一个消息被多个消费者消费。工作模式是同一个消息只能有一个消费者。
@Bean public Queue AMessage() { return new Queue("fanout.A"); } @Bean public Queue BMessage() { return new Queue("fanout.B"); } @Bean public Queue CMessage() { return new Queue("fanout.C"); }
@Bean FanoutExchange fanoutExchange() { return new FanoutExchange("fanoutExchange"); }
@Bean Binding bindingExchangeA(Queue AMessage, FanoutExchange fanoutExchange) { return BindingBuilder.bind(AMessage).to(fanoutExchange); } @Bean Binding bindingExchangeB(Queue BMessage, FanoutExchange fanoutExchange) { return BindingBuilder.bind(BMessage).to(fanoutExchange); } @Bean Binding bindingExchangeC(Queue CMessage, FanoutExchange fanoutExchange) { return BindingBuilder.bind(CMessage).to(fanoutExchange); }
@Componentpublic class FanoutSender { @Autowired private AmqpTemplate rabbitTemplate; public void send() { String context = "hi, fanout msg "; System.out.println("Sender : " + context); this.rabbitTemplate.convertAndSend("fanoutExchange","", context); }}
1 @Component 2 @RabbitListener(queues = "fanout.A") 3 public class FanoutReceiveA { 4 5 @RabbitHandler 6 public void process(String message) { 7 System.out.println("fanout Receiver A : " + message); 8 } 9 }10 11 @Component12 @RabbitListener(queues = "fanout.B")13 public class FanoutReceiverB {14 @RabbitHandler15 public void process(String message) {16 System.out.println("fanout Receiver B: " + message);17 }18 }19 20 @Component21 @RabbitListener(queues = "fanout.C")22 public class FanoutReceiverC {23 @RabbitHandler24 public void process(String message) {25 System.out.println("fanout Receiver C: " + message);26 }27 }
@RunWith(SpringRunner.class)@SpringBootTestpublic class FanoutTest { @Autowired private FanoutSender fanoutSender; @Test public void setFanoutSender(){ fanoutSender.send(); } }
需要将一个队列绑定到交换机上,要求该消息与一个特定的路由键完全匹配,这是一个完整的匹配。
发送端不只按固定的routing key发送消息,而是按字符串匹配发送,接收端同样如此
final static String message = "topic.A"; final static String messages = "topic.B"; @Bean public Queue queueMessage() { return new Queue(TopicRabbitConfig.message); } @Bean public Queue queueMessages() { return new Queue(TopicRabbitConfig.messages);
@Bean TopicExchange exchange() { return new TopicExchange("topicExchange"); }
绑定队列到交换机上,路由模式,需要完整匹配topic.message,才能接受
@Bean Binding bindingExchangeMessage(Queue queueMessage, TopicExchange exchange) { return BindingBuilder.bind(queueMessage).to(exchange).with("topic.message"); }
@Bean Binding bindingExchangeMessages(Queue queueMessages, TopicExchange exchange) { return BindingBuilder.bind(queueMessages).to(exchange).with("topic.#"); }
@Componentpublic class TopicSend { @Autowired private AmqpTemplate rabbitTemplate; public void send() { String context = "hi, i am message all"; System.out.println("Sender : " + context); this.rabbitTemplate.convertAndSend("topicExchange", "topic.1", context); } public void send1() { String context = "hi, i am message 1"; System.out.println("Sender : " + context); this.rabbitTemplate.convertAndSend("topicExchange", "topic.message", context); } public void send2() { String context = "hi, i am messages 2"; System.out.println("Sender : " + context); this.rabbitTemplate.convertAndSend("topicExchange", "topic.messages", context); }}
send的key是topic.1 send1的key是topic.message,send2的key是topic.messages
所以理论上send会被两个队列消费,1.2都应该只有一个队列消费
@Component@RabbitListener(queues = "topic.A")public class TopicReceiver { @RabbitHandler public void process(String message) { System.out.println("Topic Receiver1 : " + message); } }
@Component@RabbitListener(queues = "topic.B")public class TopicReceiver2 { @RabbitHandler public void process(String message) { System.out.println("Topic Receiver2 : " + message); }}
@RunWith(SpringRunner.class)@SpringBootTestpublic class TopicTest { @Autowired private TopicSend sender; @Test public void topic() throws Exception { sender.send(); } @Test public void topic1() throws Exception { sender.send1(); } @Test public void topic2() throws Exception { sender.send2(); } }