[ 
https://issues.apache.org/jira/browse/ARTEMIS-3492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17416920#comment-17416920
 ] 

Justin Bertram commented on ARTEMIS-3492:
-----------------------------------------

As noted, the behavior you're seeing isn't a bug. The goal of ARTEMIS-3141 was 
to limit the amount of data returned from JMX QueueControl {{listMessages}} 
method (as the title indicates). Both ARTEMIS-3128 and ARTEMIS-3175 are related 
to this. In short, the behavior was changed to protect the broker (and to some 
degree the client as well) from an uncontrolled volume of message data which 
might have adverse results. You can peruse all those Jiras to get more details 
about why the behavior was changed.

You should be able to restore the previous behavior by using 
{{<management-message-attribute-size-limit>-1</management-message-attribute-size-limit>}},
 but I would caution you against that as it removes the new protections. I 
would encourage you to find a reasonable limit that fits your use-case and 
specify that instead.

> Not able to view full payload in artemis 2.18 console
> -----------------------------------------------------
>
>                 Key: ARTEMIS-3492
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-3492
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: Broker, Web Console
>    Affects Versions: 2.18.0
>         Environment: all env's. 
>            Reporter: Ekta
>            Priority: Major
>
> Hello,
> We recently moved to 2.18 version from 2.17. So far we are seeing lot of 
> improvements but all of the sudden we found in 2.18 when there are messages 
> sitting in queue, while browsing them we are not able to view full payload 
> and it is only showing few lines and then shows + 11150 more. We are 
> suspecting this is the bug itself in 2.18 as it did not exist in 2.17. If 
> anyone have a workaround or way to extract the full payload will really help 
> until there is a fix for this. We have tried all the browse options from 
> console but no luck. 
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to