[jira] [Resolved] (ARTEMIS-66) implement configuration persistence

["Justin Bertram (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/ARTEMIS-66?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Justin Bertram resolved ARTEMIS-66.
-----------------------------------
    Fix Version/s:     (was: unscheduled)
       Resolution: Won't Fix

Durable resources created at runtime (e.g. via JMX management operations or auto-created by the broker) are not added to {{broker.xml}} by design. Updating {{broker.xml}} for every resource created could severely impact broker performance. For example, the broker can serve thousands of clients simultaneously potentially auto-creating addresses and queues almost constantly. Having to update a potentially large XML file in a thread-safe way would be a significant bottleneck. 

Furthermore, {{broker.xml}} can be assembled from many different files using {{xinclude}}. This functionality is provided transparently by the underlying XML parser from the JVM. Implementing configuration persistence would require a complete reimplementation of this functionality.

Currently durable resources created at runtime are stored in the "bindings" journal which uses the same technology as the high performance message journal. All the resources from the bindings journal are reloaded when the broker restarts just like resources configured directly in {{broker.xml}}.

> implement configuration persistence
> -----------------------------------
>
>                 Key: ARTEMIS-66
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-66
>             Project: ActiveMQ Artemis
>          Issue Type: New Feature
>            Reporter: Andy Taylor
>            Priority: Major
>
> We should reflect changes thru management such as adding destinations in the configuration file.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)