[jira] [Commented] (ARTEMIS-3531) adding documentation for management-message-attribute-size-limit
[ https://issues.apache.org/jira/browse/ARTEMIS-3531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17432319#comment-17432319 ] ASF subversion and git services commented on ARTEMIS-3531: -- Commit 99ed1a705601d0053f7f290243c0f3de0ddc5e00 in activemq-artemis's branch refs/heads/main from Erwin Dondorp [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=99ed1a7 ] ARTEMIS-3531 added documentation for address-setting "management-message-attribute-size-limit" > adding documentation for management-message-attribute-size-limit > > > Key: ARTEMIS-3531 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3531 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: Configuration >Affects Versions: 2.18.0, 2.19.0 >Reporter: Erwin Dondorp >Priority: Minor > Time Spent: 40m > Remaining Estimate: 0h > > The documentation pages do not mention configuration parameter > `management-message-attribute-size-limit`. This parameter is used to control > which part (size) of the messages can be browsed. it was introduced in 2.18.0 > to solve out-of-memory problems. > PR will be supplied... -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ARTEMIS-3531) adding documentation for management-message-attribute-size-limit
[ https://issues.apache.org/jira/browse/ARTEMIS-3531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17432320#comment-17432320 ] ASF subversion and git services commented on ARTEMIS-3531: -- Commit 524bc7bd715ce74ee6ab7a55ca01cc2ee3a46bbf in activemq-artemis's branch refs/heads/main from Erwin Dondorp [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=524bc7b ] ARTEMIS-3531 after review comment from gtully > adding documentation for management-message-attribute-size-limit > > > Key: ARTEMIS-3531 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3531 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: Configuration >Affects Versions: 2.18.0, 2.19.0 >Reporter: Erwin Dondorp >Priority: Minor > Time Spent: 40m > Remaining Estimate: 0h > > The documentation pages do not mention configuration parameter > `management-message-attribute-size-limit`. This parameter is used to control > which part (size) of the messages can be browsed. it was introduced in 2.18.0 > to solve out-of-memory problems. > PR will be supplied... -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ARTEMIS-3531) adding documentation for management-message-attribute-size-limit
[ https://issues.apache.org/jira/browse/ARTEMIS-3531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17431033#comment-17431033 ] arne anka commented on ARTEMIS-3531: [~erwindon] So? My comment explicitly addressed that – and added emphasis to it's priority mismatch. Documentation _must not_ be a separate issue and at low priority at that. > adding documentation for management-message-attribute-size-limit > > > Key: ARTEMIS-3531 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3531 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: Configuration >Affects Versions: 2.18.0, 2.19.0 >Reporter: Erwin Dondorp >Priority: Minor > Time Spent: 40m > Remaining Estimate: 0h > > The documentation pages do not mention configuration parameter > `management-message-attribute-size-limit`. This parameter is used to control > which part (size) of the messages can be browsed. it was introduced in 2.18.0 > to solve out-of-memory problems. > PR will be supplied... -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ARTEMIS-3531) adding documentation for management-message-attribute-size-limit
[ https://issues.apache.org/jira/browse/ARTEMIS-3531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17430714#comment-17430714 ] Erwin Dondorp commented on ARTEMIS-3531: [~2020-11-12] this PR is only about a documentation update. this is independent of the working of that option. please raise a separate bug report when you think there is a problem there. note that I successfully used this option to raise the limit from the default 256 to 2048. > adding documentation for management-message-attribute-size-limit > > > Key: ARTEMIS-3531 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3531 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: Configuration >Affects Versions: 2.18.0, 2.19.0 >Reporter: Erwin Dondorp >Priority: Minor > Time Spent: 40m > Remaining Estimate: 0h > > The documentation pages do not mention configuration parameter > `management-message-attribute-size-limit`. This parameter is used to control > which part (size) of the messages can be browsed. it was introduced in 2.18.0 > to solve out-of-memory problems. > PR will be supplied... -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ARTEMIS-3531) adding documentation for management-message-attribute-size-limit
[ https://issues.apache.org/jira/browse/ARTEMIS-3531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17430477#comment-17430477 ] arne anka commented on ARTEMIS-3531: I don't see how documentation for change qualifying for a mention in the short release information can be classified as "minor". Would someone at least add the information here as to where and how to configure that setting? Currently it is breaking parts of my workflow and I need to fix that. > adding documentation for management-message-attribute-size-limit > > > Key: ARTEMIS-3531 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3531 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: Configuration >Affects Versions: 2.18.0, 2.19.0 >Reporter: Erwin Dondorp >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > The documentation pages do not mention configuration parameter > `management-message-attribute-size-limit`. This parameter is used to control > which part (size) of the messages can be browsed. it was introduced in 2.18.0 > to solve out-of-memory problems. > PR will be supplied... -- This message was sent by Atlassian Jira (v8.3.4#803005)
