Activemq和Rabbitmq端口冲突

最新推荐文章于 2024-06-16 01:18:52 发布
最新推荐文章于 2024-06-16 01:18:52 发布
阅读量1.3k 收藏
点赞数
分类专栏： ActiveMq
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/zhangjianming2018/article/details/117855006
版权

今天调试一个项目用到了activeMq，于是下载 apache-activemq-5.16.2 启动失败


C:\WINDOWS\system32>cd D:\apache-activemq-5.16.2\bin

C:\WINDOWS\system32>d:

D:\apache-activemq-5.16.2\bin>activemq start
Java Runtime: Oracle Corporation 1.8.0_161 C:\Program Files\Java\jdk1.8.0_161\jre
  Heap sizes: current=1005056k  free=989327k  max=1005056k
    JVM args: -Dcom.sun.management.jmxremote -Xms1G -Xmx1G -Djava.util.logging.config.file=logging.properties -Djava.security.auth.login.config=D:\apache-activemq-5.16.2\bin\..\conf\login.config -Dactivemq.classpath=D:\apache-activemq-5.16.2\bin\..\conf;D:\apache-activemq-5.16.2\bin\../conf;D:\apache-activemq-5.16.2\bin\../conf; -Dactivemq.home=D:\apache-activemq-5.16.2\bin\.. -Dactivemq.base=D:\apache-activemq-5.16.2\bin\.. -Dactivemq.conf=D:\apache-activemq-5.16.2\bin\..\conf -Dactivemq.data=D:\apache-activemq-5.16.2\bin\..\data -Djava.io.tmpdir=D:\apache-activemq-5.16.2\bin\..\data\tmp
Extensions classpath:
  [D:\apache-activemq-5.16.2\bin\..\lib,D:\apache-activemq-5.16.2\bin\..\lib\camel,D:\apache-activemq-5.16.2\bin\..\lib\optional,D:\apache-activemq-5.16.2\bin\..\lib\web,D:\apache-activemq-5.16.2\bin\..\lib\extra]
ACTIVEMQ_HOME: D:\apache-activemq-5.16.2\bin\..
ACTIVEMQ_BASE: D:\apache-activemq-5.16.2\bin\..
ACTIVEMQ_CONF: D:\apache-activemq-5.16.2\bin\..\conf
ACTIVEMQ_DATA: D:\apache-activemq-5.16.2\bin\..\data
Loading message broker from: xbean:activemq.xml
 INFO | Refreshing org.apache.activemq.xbean.XBeanBrokerFactory$1@4f970963: startup date [Sat Jun 12 20:02:50 CST 2021]; root of context hierarchy
 INFO | Using Persistence Adapter: KahaDBPersistenceAdapter[D:\apache-activemq-5.16.2\bin\..\data\kahadb]
 INFO | KahaDB is version 7
 INFO | PListStore:[D:\apache-activemq-5.16.2\bin\..\data\localhost\tmp_storage] started
 INFO | Apache ActiveMQ 5.16.2 (localhost, ID:LAPTOP-3K7R226R-63012-1623499371742-0:1) is starting
 INFO | Listening for connections at: tcp://LAPTOP-3K7R226R:61616?maximumConnections=1000&wireFormat.maxFrameSize=104857600
 INFO | Connector openwire started
ERROR | Failed to start Apache ActiveMQ (localhost, ID:LAPTOP-3K7R226R-63012-1623499371742-0:1)
java.io.IOException: Transport Connector could not be registered in JMX: java.io.IOException: Failed to bind to server socket: amqp://0.0.0.0:5672?maximumConnections=1000&wireFormat.maxFrameSize=104857600 due to: java.net.BindException: Address already in use: JVM_Bind
        at org.apache.activemq.util.IOExceptionSupport.create(IOExceptionSupport.java:28)
        at org.apache.activemq.broker.BrokerService.registerConnectorMBean(BrokerService.java:2288)
        at org.apache.activemq.broker.BrokerService.startTransportConnector(BrokerService.java:2769)
        at org.apache.activemq.broker.BrokerService.startAllConnectors(BrokerService.java:2665)
        at org.apache.activemq.broker.BrokerService.doStartBroker(BrokerService.java:780)
        at org.apache.activemq.broker.BrokerService.startBroker(BrokerService.java:742)
        at org.apache.activemq.broker.BrokerService.start(BrokerService.java:645)
        at org.apache.activemq.xbean.XBeanBrokerService.afterPropertiesSet(XBeanBrokerService.java:73)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeCustomInitMethod(AbstractAutowireCapableBeanFactory.java:1748)
        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1685)
        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1615)
        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:553)
        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:481)
        at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:312)
        at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:230)
        at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:308)
        at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:197)
        at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:756)
        at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:867)
        at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:542)
        at org.apache.xbean.spring.context.ResourceXmlApplicationContext.<init>(ResourceXmlApplicationContext.java:64)
        at org.apache.xbean.spring.context.ResourceXmlApplicationContext.<init>(ResourceXmlApplicationContext.java:52)
        at org.apache.activemq.xbean.XBeanBrokerFactory$1.<init>(XBeanBrokerFactory.java:104)
        at org.apache.activemq.xbean.XBeanBrokerFactory.createApplicationContext(XBeanBrokerFactory.java:104)
        at org.apache.activemq.xbean.XBeanBrokerFactory.createBroker(XBeanBrokerFactory.java:67)
        at org.apache.activemq.broker.BrokerFactory.createBroker(BrokerFactory.java:71)
        at org.apache.activemq.broker.BrokerFactory.createBroker(BrokerFactory.java:54)
        at org.apache.activemq.console.command.StartCommand.runTask(StartCommand.java:87)
        at org.apache.activemq.console.command.AbstractCommand.execute(AbstractCommand.java:63)
        at org.apache.activemq.console.command.ShellCommand.runTask(ShellCommand.java:154)
        at org.apache.activemq.console.command.AbstractCommand.execute(AbstractCommand.java:63)
        at org.apache.activemq.console.command.ShellCommand.main(ShellCommand.java:104)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at org.apache.activemq.console.Main.runTaskClass(Main.java:262)
        at org.apache.activemq.console.Main.main(Main.java:115)
Caused by: java.io.IOException: Failed to bind to server socket: amqp://0.0.0.0:5672?maximumConnections=1000&wireFormat.maxFrameSize=104857600 due to: java.net.BindException: Address already in use: JVM_Bind
        at org.apache.activemq.util.IOExceptionSupport.create(IOExceptionSupport.java:34)
        at org.apache.activemq.transport.tcp.TcpTransportServer.bind(TcpTransportServer.java:146)
        at org.apache.activemq.transport.tcp.TcpTransportFactory.doBind(TcpTransportFactory.java:62)
        at org.apache.activemq.transport.TransportFactorySupport.bind(TransportFactorySupport.java:40)
        at org.apache.activemq.broker.TransportConnector.createTransportServer(TransportConnector.java:335)
        at org.apache.activemq.broker.TransportConnector.getServer(TransportConnector.java:145)
        at org.apache.activemq.broker.TransportConnector.asManagedConnector(TransportConnector.java:110)
        at org.apache.activemq.broker.BrokerService.registerConnectorMBean(BrokerService.java:2283)
        ... 40 more
Caused by: java.net.BindException: Address already in use: JVM_Bind
        at java.net.DualStackPlainSocketImpl.bind0(Native Method)
        at java.net.DualStackPlainSocketImpl.socketBind(DualStackPlainSocketImpl.java:106)
        at java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:387)
        at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:190)
        at java.net.ServerSocket.bind(ServerSocket.java:375)
        at java.net.ServerSocket.<init>(ServerSocket.java:237)
        at javax.net.DefaultServerSocketFactory.createServerSocket(ServerSocketFactory.java:231)
        at org.apache.activemq.transport.tcp.TcpTransportServer.bind(TcpTransportServer.java:143)
        ... 46 more
 INFO | Apache ActiveMQ 5.16.2 (localhost, ID:LAPTOP-3K7R226R-63012-1623499371742-0:1) is shutting down
 INFO | Connector openwire stopped
 INFO | Connector amqp stopped
 INFO | Connector stomp stopped
 INFO | Connector mqtt stopped
 INFO | Connector ws stopped
 INFO | PListStore:[D:\apache-activemq-5.16.2\bin\..\data\localhost\tmp_storage] stopped
 INFO | Stopping async queue tasks
 INFO | Stopping async topic tasks
 INFO | Stopped KahaDB
 INFO | Apache ActiveMQ 5.16.2 (localhost, ID:LAPTOP-3K7R226R-63012-1623499371742-0:1) uptime 0.847 seconds
 INFO | Apache ActiveMQ 5.16.2 (localhost, ID:LAPTOP-3K7R226R-63012-1623499371742-0:1) is shutdown
 INFO | Closing org.apache.activemq.xbean.XBeanBrokerFactory$1@4f970963: startup date [Sat Jun 12 20:02:50 CST 2021]; root of context hierarchy
 WARN | Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.apache.activemq.xbean.XBeanBrokerService#0' defined in class path resource [activemq.xml]: Invocation of init method failed; nested exception is java.io.IOException: Transport Connector could not be registered in JMX: java.io.IOException: Failed to bind to server socket: amqp://0.0.0.0:5672?maximumConnections=1000&wireFormat.maxFrameSize=104857600 due to: java.net.BindException: Address already in use: JVM_Bind
ERROR: java.lang.RuntimeException: Failed to execute start task. Reason: java.lang.IllegalStateException: BeanFactory not initialized or already closed - call 'refresh' before accessing beans via the ApplicationContext
java.lang.RuntimeException: Failed to execute start task. Reason: java.lang.IllegalStateException: BeanFactory not initialized or already closed - call 'refresh' before accessing beans via the ApplicationContext
        at org.apache.activemq.console.command.StartCommand.runTask(StartCommand.java:91)
        at org.apache.activemq.console.command.AbstractCommand.execute(AbstractCommand.java:63)
        at org.apache.activemq.console.command.ShellCommand.runTask(ShellCommand.java:154)
        at org.apache.activemq.console.command.AbstractCommand.execute(AbstractCommand.java:63)
        at org.apache.activemq.console.command.ShellCommand.main(ShellCommand.java:104)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at org.apache.activemq.console.Main.runTaskClass(Main.java:262)
        at org.apache.activemq.console.Main.main(Main.java:115)
Caused by: java.lang.IllegalStateException: BeanFactory not initialized or already closed - call 'refresh' before accessing beans via the ApplicationContext
        at org.springframework.context.support.AbstractRefreshableApplicationContext.getBeanFactory(AbstractRefreshableApplicationContext.java:164)
        at org.springframework.context.support.AbstractApplicationContext.destroyBeans(AbstractApplicationContext.java:1034)
        at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:555)
        at org.apache.xbean.spring.context.ResourceXmlApplicationContext.<init>(ResourceXmlApplicationContext.java:64)
        at org.apache.xbean.spring.context.ResourceXmlApplicationContext.<init>(ResourceXmlApplicationContext.java:52)
        at org.apache.activemq.xbean.XBeanBrokerFactory$1.<init>(XBeanBrokerFactory.java:104)
        at org.apache.activemq.xbean.XBeanBrokerFactory.createApplicationContext(XBeanBrokerFactory.java:104)
        at org.apache.activemq.xbean.XBeanBrokerFactory.createBroker(XBeanBrokerFactory.java:67)
        at org.apache.activemq.broker.BrokerFactory.createBroker(BrokerFactory.java:71)
        at org.apache.activemq.broker.BrokerFactory.createBroker(BrokerFactory.java:54)
        at org.apache.activemq.console.command.StartCommand.runTask(StartCommand.java:87)
        ... 10 more
ERROR: java.lang.IllegalStateException: BeanFactory not initialized or already closed - call 'refresh' before accessing beans via the ApplicationContext
java.lang.IllegalStateException: BeanFactory not initialized or already closed - call 'refresh' before accessing beans via the ApplicationContext
        at org.springframework.context.support.AbstractRefreshableApplicationContext.getBeanFactory(AbstractRefreshableApplicationContext.java:164)
        at org.springframework.context.support.AbstractApplicationContext.destroyBeans(AbstractApplicationContext.java:1034)
        at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:555)
        at org.apache.xbean.spring.context.ResourceXmlApplicationContext.<init>(ResourceXmlApplicationContext.java:64)
        at org.apache.xbean.spring.context.ResourceXmlApplicationContext.<init>(ResourceXmlApplicationContext.java:52)
        at org.apache.activemq.xbean.XBeanBrokerFactory$1.<init>(XBeanBrokerFactory.java:104)
        at org.apache.activemq.xbean.XBeanBrokerFactory.createApplicationContext(XBeanBrokerFactory.java:104)
        at org.apache.activemq.xbean.XBeanBrokerFactory.createBroker(XBeanBrokerFactory.java:67)
        at org.apache.activemq.broker.BrokerFactory.createBroker(BrokerFactory.java:71)
        at org.apache.activemq.broker.BrokerFactory.createBroker(BrokerFactory.java:54)
        at org.apache.activemq.console.command.StartCommand.runTask(StartCommand.java:87)
        at org.apache.activemq.console.command.AbstractCommand.execute(AbstractCommand.java:63)
        at org.apache.activemq.console.command.ShellCommand.runTask(ShellCommand.java:154)
        at org.apache.activemq.console.command.AbstractCommand.execute(AbstractCommand.java:63)
        at org.apache.activemq.console.command.ShellCommand.main(ShellCommand.java:104)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at org.apache.activemq.console.Main.runTaskClass(Main.java:262)
        at org.apache.activemq.console.Main.main(Main.java:115)
D:\apache-activemq-5.16.2\bin>

端口5672被占用了！

使用cmd命令行查到被erl.exe占用了，想到这不是RabbitMQ的服务嘛

D:\apache-activemq-5.16.2\bin>netstat -aon | findstr "5672"
  TCP    0.0.0.0:5672           0.0.0.0:0              LISTENING       6000
  TCP    0.0.0.0:15672          0.0.0.0:0              LISTENING       6000
  TCP    0.0.0.0:25672          0.0.0.0:0              LISTENING       6000
  TCP    127.0.0.1:15672        127.0.0.1:63042        TIME_WAIT       0
  TCP    127.0.0.1:15672        127.0.0.1:63206        ESTABLISHED     6000
  TCP    127.0.0.1:63206        127.0.0.1:15672        ESTABLISHED     17192
  TCP    [::]:5672              [::]:0                 LISTENING       6000

D:\apache-activemq-5.16.2\bin>

 其中的一个项目是使用的RabbitMQ消息队列，所以命令行一直起着，但总不能为了一个ActiveMQ就不能用RabbitMQ吧，在网上搜索了一番，发现ActiveMQ的5672端口号是可以改动的。

 

解决方案：

修改D:\apache-activemq-5.16.2\conf\activemq.xml文件，搜索端口号5672，将其改为5673，保存后重新启动activemq即可！


D:\apache-activemq-5.16.2\bin>activemq start
Java Runtime: Oracle Corporation 1.8.0_161 C:\Program Files\Java\jdk1.8.0_161\jre
  Heap sizes: current=1005056k  free=989327k  max=1005056k
    JVM args: -Dcom.sun.management.jmxremote -Xms1G -Xmx1G -Djava.util.logging.config.file=logging.properties -Djava.security.auth.login.config=D:\apache-activemq-5.16.2\bin\..\conf\login.config -Dactivemq.classpath=D:\apache-activemq-5.16.2\bin\..\conf;D:\apache-activemq-5.16.2\bin\../conf;D:\apache-activemq-5.16.2\bin\../conf; -Dactivemq.home=D:\apache-activemq-5.16.2\bin\.. -Dactivemq.base=D:\apache-activemq-5.16.2\bin\.. -Dactivemq.conf=D:\apache-activemq-5.16.2\bin\..\conf -Dactivemq.data=D:\apache-activemq-5.16.2\bin\..\data -Djava.io.tmpdir=D:\apache-activemq-5.16.2\bin\..\data\tmp
Extensions classpath:
  [D:\apache-activemq-5.16.2\bin\..\lib,D:\apache-activemq-5.16.2\bin\..\lib\camel,D:\apache-activemq-5.16.2\bin\..\lib\optional,D:\apache-activemq-5.16.2\bin\..\lib\web,D:\apache-activemq-5.16.2\bin\..\lib\extra]
ACTIVEMQ_HOME: D:\apache-activemq-5.16.2\bin\..
ACTIVEMQ_BASE: D:\apache-activemq-5.16.2\bin\..
ACTIVEMQ_CONF: D:\apache-activemq-5.16.2\bin\..\conf
ACTIVEMQ_DATA: D:\apache-activemq-5.16.2\bin\..\data
Loading message broker from: xbean:activemq.xml
 INFO | Refreshing org.apache.activemq.xbean.XBeanBrokerFactory$1@4f970963: startup date [Sat Jun 12 20:11:15 CST 2021]; root of context hierarchy
 INFO | Using Persistence Adapter: KahaDBPersistenceAdapter[D:\apache-activemq-5.16.2\bin\..\data\kahadb]
 INFO | KahaDB is version 7
 INFO | PListStore:[D:\apache-activemq-5.16.2\bin\..\data\localhost\tmp_storage] started
 INFO | Apache ActiveMQ 5.16.2 (localhost, ID:LAPTOP-3K7R226R-63494-1623499876924-0:1) is starting
 INFO | Listening for connections at: tcp://LAPTOP-3K7R226R:61616?maximumConnections=1000&wireFormat.maxFrameSize=104857600
 INFO | Connector openwire started
 INFO | Listening for connections at: amqp://LAPTOP-3K7R226R:5673?maximumConnections=1000&wireFormat.maxFrameSize=104857600
 INFO | Connector amqp started
 INFO | Listening for connections at: stomp://LAPTOP-3K7R226R:61613?maximumConnections=1000&wireFormat.maxFrameSize=104857600
 INFO | Connector stomp started
 INFO | Listening for connections at: mqtt://LAPTOP-3K7R226R:1883?maximumConnections=1000&wireFormat.maxFrameSize=104857600
 INFO | Connector mqtt started
 INFO | Starting Jetty server
 INFO | Creating Jetty connector
 WARN | ServletContext@o.e.j.s.ServletContextHandler@6995bf68{/,null,STARTING} has uncovered http methods for path: /
 INFO | Listening for connections at ws://LAPTOP-3K7R226R:61614?maximumConnections=1000&wireFormat.maxFrameSize=104857600
 INFO | Connector ws started
 INFO | Apache ActiveMQ 5.16.2 (localhost, ID:LAPTOP-3K7R226R-63494-1623499876924-0:1) started
 INFO | For help or more information please see: http://activemq.apache.org
 INFO | ActiveMQ WebConsole available at http://127.0.0.1:8161/
 INFO | ActiveMQ Jolokia REST API available at http://127.0.0.1:8161/api/jolokia/

 

zhangjianming2018
关注
  • 0
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 1
    评论
专栏目录
rabbitMQ和ActiveMQ发生端口冲突解决办法
不怕万人阻挡，只怕自己投降
10-02 2001
如果rabbitMQ和ActiveMQ同时安装在虚拟机中，一个可以正常启动，一个则启动不成功，首先考虑到的应该是有可能会发生端口冲突！发生冲突以后修改任意一个的端口就能解决问题。解决办法如下（修改activemq的端口）： （1）转到activemq的安装目录conf （2）进入conf文件夹，打开activemq.xml (3)找到下面这行代码，修改里面的端口（把原来原来的5672改成5673）...
Window 下ActiveMQ端口冲突,负载均衡,主备配置
topMan'blog
07-17 219
           在Java 学习中Window操作系统下，类似ActiveMQ，Tomcat服务开启服务之后，服务在后台执行，经常遇到端口被占用该怎么办呢？可能多少童鞋都是进行修改端口或者重启相关的服务，但是重新启动之后，相关的端口仍然被占用。我们可能查找进程并kill进程。 在window系统下：      查看进程号： 　　　  netstat  -ano | find "被占...
[报错解决]Failed to bind to server socket: amqp://0.0.0.0:5672?maximumConnections
最新发布
WLKUYM的博客
06-16 384
服务器套接字时失败了， 使用的地址是 amqp://0.0.0.0:5672󠁪 并且设置了最大连接数的参数。遇到这个问题，意味着您的应用程序在尝试绑定到AMQP (Advanced Message Queuing Protocol)
activeMq与rabbitmq端口冲突
shen_yun2017的博客
03-22 653
activeMq与rabbitmq端口冲突 当安装activeMq时出现如下错误 修改方法将安装目录下的xml配置修改下的端口号修改为5673. <transportConnector name="amqp" uri="amqp://0.0.0.0:5673?maximumConnections=1000&amp;wireFormat.maxFrameSize=10485760...
ActiveMq端口被占用的方案
没有伞的孩子必须努力奔跑！—小林
03-26 926
1.   netstat -aon | findstr "61616"      查询进程id2. taskkill /f /pid 332256                    杀死进程
activemq和rabbitmq测试工具.rar
10-02
本资源提供了一款针对ActiveMQ和RabbitMQ的测试工具，支持RabbitMQ的MQTT协议和AMQP协议，为开发者提供了方便的生产者和消费者源码，适用于VS2008编译环境。 首先，让我们深入了解ActiveMQ和RabbitMQ这两个主流的...
ActiveMQ / RabbitMQ 示例
04-20
本示例主要关注三个流行的消息队列服务：ActiveMQ、RabbitMQ以及AliyunMQ，它们都是基于Java消息服务（JMS）的实现。 首先，ActiveMQ是由Apache开发的开源消息代理，它是JMS 1.1规范的实现者。ActiveMQ支持多种协议...
浅谈Java消息队列总结篇（ActiveMQ、RabbitMQ、ZeroMQ、Kafka）
08-25
常用的消息队列有 ActiveMQ、RabbitMQ、ZeroMQ、Kafka、MetaMQ、RocketMQ 等。 Java 消息队列的应用场景： 1. 异步处理：引入消息队列，将不是必须的业务逻辑异步处理，解决系统性能瓶颈问题。 2. 应用解耦：引入...
ActiveMQ RabbitMQ RokcetMQ 消息队列中间件视频教程
12-24
作为消息中间件的MQ在java开发中起着举足轻重的地位，无论是ActiveMQ、RabbitMQ、还是RokcetMQ至少要会一个，否则别说自己是java程序员。Java自学网整理了目前行业最常用的消息中间件视频供大家学习。
38 3 ActiveMQ RabbitMQ RokcetMQ Kafka实战 消息队列中间件视频教程
08-07
ActiveMQ RabbitMQ RokcetMQ Kafka实战 消息队列中间件视频教程
RabbitMQ & ActiveMQ 共存 - Broker 端口冲突
weixin_30326745的博客
02-08 749
问题：在测试机器上安装了activeMQ和RabbitMQ，但是启动的时候只能启动其中的一个。网上查找是因为他们端口冲突了。5672和61613. 为此上网找到的结果是： 但是找了半天也没找到rabbitmq的配置文件，于是心想那我就更改activemq的配置文件不也行嘛，所以我就更改了activemq的配置文件。 其位置在：/home/mq/apache-activemq-5.14.0...
因为ActiveMQ的配置文件只允许127.0.0.1访问导致的内网其他电脑无法访问我的activemq
过客的博客
12-12 1万+
17:05:50.790 [main] DEBUG org.apache.activemq.util.ThreadPoolUtils - Shutdown of ExecutorService: java.util.concurrent.ThreadPoolExecutor@5cc7c2a6[Terminated, pool size = 0, active threads = 0, queue...
Exception encountered during context initialization - cancelling refresh attempt--依赖缺失
青山的博客
03-10 1577
Exception encountered during context initialization - cancelling refresh attempt:
警告: Exception encountered during context initialization - cancelling refresh attempt
热门推荐
Barnes3255的博客
08-08 1万+
debug
zookeeper+ActiveMQ集群启动后无法访问
九尾狐的yi巴的博客
07-08 1819
zookeeper和ActiveMQ进程都在，但是MQ无法使用，也不能访问MQ的管理页面，其实还是没真正的启动。 搜了一圈，还是认为是有脏数据，但是并不像是在启动或停止服务的时候有发mq消息导致的。因为今天我就没运行代码他怎么发？？！！！ 最后还是得删除leveldb文件夹才行。将全部节点的./apache-activemq/data/leveldb文件夹删了就能启动了。铁憨憨设计！！！ 截取报错信息： 2020-07-10 10:06:56,232 | WARN | unprocesse...
activemq java.io.eofexception,ActiveMQ启动时，警告为java.io.EOFException
weixin_29170089的博客
02-28 2206
am trying to start the ActiveMQ 5.11 and I see a WARNING as below:WARN | Transport Connection to: tcp://127.0.0.1:40890 failed: java.io.EOFExceptionMy activemq.xml is as below:keyStore="file:${JMS_KEY...
ActiveMQ常见错误二:javax.jms.JMSException: Unknown data type: 47
漫天雪_昆仑巅
06-30 1万+
Java连接ActiveMQ时报错： javax.jms.JMSException: Unknown data type: 47 at org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:72) at org.apache.activemq.ActiveMQConnection.sy
ActiveMQ 启动时报错
SIMBA1949的博客
10-01 2210
ActiveMQ 启动时报错 错误详情 java.lang.IllegalStateException: BeanFactory not initialized or already closed - call ‘refresh’ before accessing beans via the ApplicationContext wrapper | --&gt; Wrapper Started ...
activemq和rabbitmq的区别
05-12
ActiveMQ和RabbitMQ都是流行的消息队列（Message Queue）软件，它们可以在分布式系统中进行消息传递、异步通信和解耦等操作。它们的主要区别如下： 1. 语言支持：ActiveMQ是用Java编写的，而RabbitMQ是用Erlang编写...
评论 1
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值