> Are there any issues having over 11,000 addresses defined in Apache Artemis?
The answer to your question really depends on your operating environment and use-case. Is the broker running out of memory? Is 11,000 addresses more than you expect? If you answered yes to either of these it may be a problem. Otherwise the broker is happy to chug along with thousands of addresses. There is no arbitrary limit to the number of addresses the broker can support. > Is this scalable? Generally speaking, yes. ActiveMQ Artemis was written specifically with scale in mind. Of course, everything has its limit so eventually you'll need to stop scaling, but the limit really depends on your performance requirements and runtime broker resources. > I do notice the management interface is a bit slow from loading all the address information. This is a known issue in the current web console. The culprit is likely the "tree" view. To build this view the browser asks the Jolokia agent running in the broker's JVM to build a JSON payload including potentially *every* MBean (including all of the attributes for each MBean). By default this data is refreshed every 5 seconds. You can see how this would become a problem with lots of addresses. That said, the web console's behavior is configurable. Go to the "Preferences" (available from the menu in the top right) and click the "Jolokia" tab. Here you can turn off auto-refresh (i.e. "Update rate"). You can also decrease the amount of data fetched by lowering the "Max depth" and "Max collection size." This is, in part, why the new console [1] doesn't have the tree view any longer. Justin [1] https://github.com/apache/activemq-artemis-console On Wed, Dec 11, 2024 at 1:01 PM William Crowell <wcrow...@perforce.com.invalid> wrote: > Hi, > > I am using Apache Artemis 2.31.2 on Ubuntu. Are there any issues having > over 11,000 addresses defined in Apache Artemis? Is this scalable? I do > notice the management interface is a bit slow from loading all the address > information. > > Regards, > > William Crowell > > > This e-mail may contain information that is privileged or confidential. If > you are not the intended recipient, please delete the e-mail and any > attachments and notify us immediately. > >
