[
https://issues.apache.org/jira/browse/ARTEMIS-5332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17956992#comment-17956992
]
ASF subversion and git services commented on ARTEMIS-5332:
----------------------------------------------------------
Commit ce5ef31c38256631e8d86c20b6e89409676086a9 in activemq-artemis's branch
refs/heads/main from Gary Tully
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=ce5ef31c38 ]
ARTEMIS-5332 avoid thread local utils bean as it will leak a builder
> add exportConfigAsProperties operation to server control
> --------------------------------------------------------
>
> Key: ARTEMIS-5332
> URL: https://issues.apache.org/jira/browse/ARTEMIS-5332
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: Configuration, management
> Affects Versions: 2.39.0
> Reporter: Gary Tully
> Assignee: Gary Tully
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.40.0
>
> Time Spent: 5h
> Remaining Estimate: 0h
>
> With broker properties, it is non trivial to figure out the syntax as it
> reflects the internal structure of the broker configuration bean and its
> composites.
> having a way to see the effective config, with all default values in play
> would be useful even with just xml config.
> The broker sets java.io.tmpdir to instance/tmp when it is unset, we can write
> a file there with the current broker config in properties format. That should
> be writable, if not, the operation fail.
> we can use the existing rbac to control access to this operation.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact
