[jira] [Commented] (ARTEMIS-4301) Resource leakage / ignored configuration
[
https://issues.apache.org/jira/browse/ARTEMIS-4301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17846286#comment-17846286
]
Daniel Martin commented on ARTEMIS-4301:
Why aren't they generally recommended? Wouldn't this lead to a resource leak of
all auto-created addresses and queues?
I understand the documentation is {_}technically correct{_}. However, it is
still worth pointing out that there is a second level of defaults that will
override the first in important practical scenarios.
By the way, why would the default value be {{true}} {_}anywhere{_}, if they are
not recommended? I find that unsettling.
> Resource leakage / ignored configuration
>
>
> Key: ARTEMIS-4301
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4301
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 2.28.0
>Reporter: Daniel Martin
>Assignee: Justin Bertram
>Priority: Critical
>
> I have an MQTT client connecting to the ActiveMQ Artemis broker. The client
> connects with a {{sessionExpiryInterval}} of 60 seconds. Among my
> {{}} in {{{}broker.xml{}}}, I have
> {{{}true{}}}. When I restart the
> MQTT client process, I can see in the broker's logs that the disconnect
> message is received and, after 60 seconds, the "session state" is removed.
> However, every time I restart the client, the queue count in a few addresses
> increases by one, and never decreases after that. Inspecting the queues, they
> all have a message count of 0, and all but the one corresponding to the
> currently-active client have a consumer count of 0. Furthermore, when
> inspecting the queue's attributes, they are all marked as "Auto delete:
> false", seemingly ignoring the setting in {{{}broker.xml{}}}.
> A secondary but still important issue: I had to manually turn queue
> auto-deletion on, as it was explicitly disabled by default, contrary to what
> is claimed in the documentation
> ([https://activemq.apache.org/components/artemis/documentation/latest/address-settings.html]).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4301) Resource leakage / ignored configuration
[
https://issues.apache.org/jira/browse/ARTEMIS-4301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17802382#comment-17802382
]
Justin Bertram commented on ARTEMIS-4301:
-
I think this will be dealt with via ARTEMIS-4501.
Also, the documentation is technically correct about the default values of
{{auto-delete-queues}} and {{auto-delete-addresses}}. They _are_ {{true}} in
the code. However, the default {{broker.xml}} generated by the {{create}}
command sets them to {{false}} explicitly since they aren't generally
recommended.
> Resource leakage / ignored configuration
>
>
> Key: ARTEMIS-4301
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4301
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 2.28.0
>Reporter: Daniel Martin
>Priority: Critical
>
> I have an MQTT client connecting to the ActiveMQ Artemis broker. The client
> connects with a {{sessionExpiryInterval}} of 60 seconds. Among my
> {{}} in {{{}broker.xml{}}}, I have
> {{{}true{}}}. When I restart the
> MQTT client process, I can see in the broker's logs that the disconnect
> message is received and, after 60 seconds, the "session state" is removed.
> However, every time I restart the client, the queue count in a few addresses
> increases by one, and never decreases after that. Inspecting the queues, they
> all have a message count of 0, and all but the one corresponding to the
> currently-active client have a consumer count of 0. Furthermore, when
> inspecting the queue's attributes, they are all marked as "Auto delete:
> false", seemingly ignoring the setting in {{{}broker.xml{}}}.
> A secondary but still important issue: I had to manually turn queue
> auto-deletion on, as it was explicitly disabled by default, contrary to what
> is claimed in the documentation
> ([https://activemq.apache.org/components/artemis/documentation/latest/address-settings.html]).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
