The OpenLogic Technical Support Team fields lots of questions on ActiveMQ and over 500 other open source packages. They’ve distilled decades of experience and hundreds of ActiveMQ support issues down to the most common questions.
| General Questions | |
|---|---|
| I have three machines on the same network. They use identical hardware and are running identical software. I need to break them into two logical broker networks (A & B). But when I try this, no matter how I configure them, they all find each other. This happens even if I specify different multicast addresses in the TCP transport connector discovery URI. What am I doing wrong? | This is a known issue with MulticastDiscoveryAgent affecting version 4.1.1 & 5.0.0 and, very likely, 5.1.0 GA as well.
For a patch to MulticastDiscoveryAgent, navigate to the ActiveMQ site. You can also read more about this issue on the ActiveMQ site. |
| We are experiencing a problem with version 5.0.0 in which the InactivityMonitor closes connections when exceptions are thrown. This interrupts message traffic and the messaging process stops functioning. | This is a known issue with ActiveMQ 5.0.0.
It has been resolved in the new official release of ActiveMQ, 5.1.0 GA. OpenLogic recommends you upgrade to this version, available in the OLEX Certified Library. |
| I need to install and configure a cluster of ActiveMQ message brokers, but several problems are hampering my efforts to get communication established between my publishing and consuming brokers. Where can I find the documentation for the latest version of ActiveMQ 5.1.x? | Detailed installation and configuration steps are available on the ActiveMQ site. |
