[
https://issues.apache.org/jira/browse/ARTEMIS-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17433046#comment-17433046
]
Justin Bertram edited comment on ARTEMIS-3535 at 10/28/21, 1:24 PM:
--------------------------------------------------------------------
[~2020-11-12], Domenico already provided a basic blue-print for providing this
information. You just need to define the steps necessary to reproduce the
problem just as he did to define the steps that did _not_ reproduce the
problem. Basic steps like this to reproduce the issue are a normal part of bug
reports. Here's another example from a test I just performed myself:
# Create an instance of a 2.18.0 broker:
{noformat}
./artemis create ARTEMIS-3535 --user myUser --password myPass
--allow-anonymous{noformat}
# Add the following to {{broker.xml}}:
{code:xml}
<address-settings>
...
<address-setting match="limitedQueue">
<management-message-attribute-size-limit>256</management-message-attribute-size-limit>
</address-setting>
<!--default for catch all-->
<address-setting match="#">
...
<management-message-attribute-size-limit>-1</management-message-attribute-size-limit>
</address-setting>
</address-settings>
...
<addresses>
...
<address name="limitedQueue">
<anycast>
<queue name="limitedQueue" />
</anycast>
</address>
<address name="unlimitedQueue">
<anycast>
<queue name="unlimitedQueue" />
</anycast>
</address>
</addresses>{code}
# Send a long message to both {{limitedQueue}} and {{ulimitedQueue}}:
{noformat}
./artemis producer --destination queue://limitedQueue --message-count 1
--text-size 5000
./artemis producer --destination queue://unlimitedQueue --message-count 1
--text-size 5000{noformat}
# View those messages in the web console. Based on the {{address-settings}} the
message in {{limitedQueue}} should be truncated at 256 characters while the
message in {{ulimitedQueue}} should be the full 5,000 characters without any
truncation. Here's what I saw:
!limited.jpg!
and
!unlimited.jpg!
As far as I can tell everything is working as expected here. Can you provide
steps like this for a use-case which _doesn't_ work as expected?
was (Author: jbertram):
[~2020-11-12], Domenico already provided a basic blue-print for providing this
information. You just need to define the steps necessary to reproduce the
problem just as he did to define the steps that did _not_ reproduce the
problem. Basic steps like this to reproduce the issue are a normal part of bug
reports. Here's another example from a test I just performed myself:
# Create an instance of a 2.18.0 broker:
{noformat}
./artemis create ARTEMIS-3535 --user myUser --password myPass
--allow-anonymous{noformat}
# Add the following to {{broker.xml}}:
{code:xml}
<address-settings>
...
<address-setting match="limitedQueue">
<management-message-attribute-size-limit>256</management-message-attribute-size-limit>
</address-setting>
<!--default for catch all-->
<address-setting match="#">
...
<management-message-attribute-size-limit>-1</management-message-attribute-size-limit>
</address-setting>
</address-settings>
...
<addresses>
...
<address name="limitedQueue">
<anycast>
<queue name="limitedQueue" />
</anycast>
</address>
<address name="unlimitedQueue">
<anycast>
<queue name="unlimitedQueue" />
</anycast>
</address>
</addresses>{code}
# Send a long message to both {{limitedQueue}} and {{ulimitedQueue}}:
{noformat}
./artemis producer --destination queue://limitedQueue --message-count 1
--text-size 5000
./artemis producer --destination queue://limitedQueue --message-count 1
--text-size 5000{noformat}
# View those messages in the web console. Based on the {{address-settings}} the
message in {{limitedQueue}} should be truncated at 256 characters while the
message in {{ulimitedQueue}} should be the full 5,000 characters without any
truncation. Here's what I saw:
!limited.jpg!
and
!unlimited.jpg!
As far as I can tell everything is working as expected here. Can you provide
steps like this for a use-case which _doesn't_ work as expected?
> management-message-attribute-size-limit = -1 does not unlimit
> -------------------------------------------------------------
>
> Key: ARTEMIS-3535
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3535
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Web Console
> Environment: A' Artems 2.19.0
> Reporter: arne anka
> Priority: Major
> Attachments: broker.xml, limited.jpg, rest.messaging.config.file.xml,
> test.xml, unlimited.jpg, web.xml
>
>
> With the new option messages are truncated.
> [https://activemq.apache.org/components/artemis/documentation/latest/versions.html]
> states for 2.18.0 that this may be overriden by using
> -1
> as value. But that doesn't work.
> {{broker.xml}}
> {code:xml}
> <address-setting match="#">
> ...
>
> <management-message-attribute-size-limit>-1</management-message-attribute-size-limit>
> </address-setting>
> {code}
> Text shown is empty.
> Changing -1 to eg 1024 text appears partially.
> Seems -1 does not work as expected.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
