activemq 嵌入式代理
在ActiveMQ中,有一个概念叫做BrokerService。通常出于学习目的,我使用启动代理的“activemq”从命令行启动代理。 以这种方式启动代理与使用 BrokerService.start(); 有什么区别?
我的猜测是,当您使用 'activemq' 时,代理将在自己的 jvm 中启动,当您使用 BrokerService.start() 时,代理将使用现有的 JVM。 这是正确的吗?
另外,如果有人能指出一个资源来解释如何在传统的 j2ee 服务器(如 weblogic)中实现代理架构,我们将不胜感激。
我主要想了解如何在集群上部署代理?
In ActiveMQ, there is a concept called BrokerService. Normally for learning purposes, I am starting the broker from the command line using 'activemq' which starts the Broker.
What is the difference between starting the broker this way and using the BrokerService.start();
My guess is that when you use 'activemq' , the broker starts in its own jvm, when you use BrokerService.start(), the broker is using the existing JVM.
Is this correct?
Also, if someone can point to a resource that explains how the broker architecture is implemented in a traditional j2ee server like weblogic, that would be much appreciated.
I am mostly seeking clarification of how a broker can be deployed on a cluster?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
查看《ActiveMQ 实践》一书。这太棒了,解释了一切
我的博客
Check out the ActiveMQ in action book. That is awesome and explains everything
My blog