[jira] [Commented] (ARTEMIS-3832) artemis create - Add option to configure address-full-policy
[
https://issues.apache.org/jira/browse/ARTEMIS-3832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17568165#comment-17568165
]
Justin Bertram commented on ARTEMIS-3832:
-
For what it's worth, the broker's CLI {{create}} command is _intentionally_
basic. It's designed to create a basic broker configuration with generally
accepted defaults. Additional customization is possible by simply modifying any
of the related text files (e.g. {{artemis.profile}}, {{broker.xml}},
{{jolokia-access.xml}}, {{login.config}}, etc.). There are just too many
options to account for all of them in the {{create}} utility. No matter what is
added it won't cover every use-case and as soon as more options are added users
will continue to ask for more and more.
I think the properties which Gary mentions are the way to go in this case.
> artemis create - Add option to configure address-full-policy
>
>
> Key: ARTEMIS-3832
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3832
> Project: ActiveMQ Artemis
> Issue Type: New Feature
> Components: Broker
>Affects Versions: 2.22.0
>Reporter: Claus Ibsen
>Priority: Major
>
> When trying out Artemis such as via a docker image, then you often run on
> limited disk space - for example I have 20gb assigned for docker.
> However Artemis may notice that its low on disk, and then go into blocking
> mode.
> It would be good if you can configure these options when creating the broker,
> especially as you use a docker file to create the image (no official release
> in docker hub etc).
> Then you can set these options via EXTRA_ARGS in the dockerfile.
> BTW: its the max-disk-usage that triggered my artemis to go into blocking
> mode, because it had detected that there was only 3gb disk left. However when
> you use Artemis for demos/examples/development, then IMHO it would be great
> if Artemis could be easily configured for such use-cases.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ARTEMIS-3832) artemis create - Add option to configure address-full-policy
[ https://issues.apache.org/jira/browse/ARTEMIS-3832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17537408#comment-17537408 ] Gary Tully commented on ARTEMIS-3832: - personally, I think a container image the used a simple jar and embedded broker with properties config is the way to go. It does not make sense to me that an image would need to go through the bare metal getting started path of artemis create etc. The existing embedded broker has some sensible defaults that can be build on. There is still some work to complete to cover all the bases with properties config, RBAC still looks odd... but I think it has promise. > artemis create - Add option to configure address-full-policy > > > Key: ARTEMIS-3832 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3832 > Project: ActiveMQ Artemis > Issue Type: New Feature > Components: Broker >Affects Versions: 2.22.0 >Reporter: Claus Ibsen >Priority: Major > > When trying out Artemis such as via a docker image, then you often run on > limited disk space - for example I have 20gb assigned for docker. > However Artemis may notice that its low on disk, and then go into blocking > mode. > It would be good if you can configure these options when creating the broker, > especially as you use a docker file to create the image (no official release > in docker hub etc). > Then you can set these options via EXTRA_ARGS in the dockerfile. > BTW: its the max-disk-usage that triggered my artemis to go into blocking > mode, because it had detected that there was only 3gb disk left. However when > you use Artemis for demos/examples/development, then IMHO it would be great > if Artemis could be easily configured for such use-cases. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (ARTEMIS-3832) artemis create - Add option to configure address-full-policy
[ https://issues.apache.org/jira/browse/ARTEMIS-3832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17537406#comment-17537406 ] Gary Tully commented on ARTEMIS-3832: - Hi Claus, I have been slowly adding support for configuration via properties files, see: https://issues.apache.org/jira/browse/ARTEMIS-3627 something like: bin/artemis run --properties /home/gtully/code/broker.properties where broker.properties has: maxDiskUsage=2.5g The broker.properties can also be resolved via a system property -Dbroker.properties=file url or path the xml in artemis is parsed mostly into a single java bean ConfigurationImpl that is used to initialise the server, most of the broker can be configured in this way, and it works nicely for any simple attribute today. > artemis create - Add option to configure address-full-policy > > > Key: ARTEMIS-3832 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3832 > Project: ActiveMQ Artemis > Issue Type: New Feature > Components: Broker >Affects Versions: 2.22.0 >Reporter: Claus Ibsen >Priority: Major > > When trying out Artemis such as via a docker image, then you often run on > limited disk space - for example I have 20gb assigned for docker. > However Artemis may notice that its low on disk, and then go into blocking > mode. > It would be good if you can configure these options when creating the broker, > especially as you use a docker file to create the image (no official release > in docker hub etc). > Then you can set these options via EXTRA_ARGS in the dockerfile. > BTW: its the max-disk-usage that triggered my artemis to go into blocking > mode, because it had detected that there was only 3gb disk left. However when > you use Artemis for demos/examples/development, then IMHO it would be great > if Artemis could be easily configured for such use-cases. -- This message was sent by Atlassian Jira (v8.20.7#820007)
