activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Lichtin (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMQ-5725) browse command emits NUL bytes when printing the body of a BytesMessage
Date Wed, 15 Apr 2015 14:08:58 GMT

     [ https://issues.apache.org/jira/browse/AMQ-5725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Martin Lichtin updated AMQ-5725:
--------------------------------
    Description: 
Using a command like

   browse --amqurl tcp://localhost:61616 myqueue

prints the headers as expected, and also prints a line like

JMS_BODY_FIELD:JMSBytes:1 = [NUL][NUL][NUL][NUL][NUL][NUL][NUL]

with a lot more [NUL] in fact. It would make more sense to print a hex representation or similar.
Or with an cmd-line option one could provide a charset and then the command could try to decode
the bytes and print as a string.

For Text messages, the body is output as expected.

JMS_BODY_FIELD:JMSText = <Message Body>

  was:
Using a command like

   browse --amqurl tcp://localhost:61616 -Vheader,custom myqueue

prints the headers as expected, but also prints a line like

JMS_BODY_FIELD:JMSBytes:1 = [NUL][NUL][NUL][NUL][NUL][NUL][NUL]

with a lot more [NUL] in fact.

As I'm not asking for the body, it should avoid printing JMS_BODY_FIELD.


     Issue Type: Improvement  (was: Bug)
        Summary: browse command emits NUL bytes when printing the body of a BytesMessage 
(was: browse command emits tons of NUL bytes when not asking to print the body)

> browse command emits NUL bytes when printing the body of a BytesMessage
> -----------------------------------------------------------------------
>
>                 Key: AMQ-5725
>                 URL: https://issues.apache.org/jira/browse/AMQ-5725
>             Project: ActiveMQ
>          Issue Type: Improvement
>    Affects Versions: 5.11.1
>         Environment: Karaf 3.0.3
>            Reporter: Martin Lichtin
>            Priority: Minor
>
> Using a command like
>    browse --amqurl tcp://localhost:61616 myqueue
> prints the headers as expected, and also prints a line like
> JMS_BODY_FIELD:JMSBytes:1 = [NUL][NUL][NUL][NUL][NUL][NUL][NUL]
> with a lot more [NUL] in fact. It would make more sense to print a hex representation
or similar.
> Or with an cmd-line option one could provide a charset and then the command could try
to decode the bytes and print as a string.
> For Text messages, the body is output as expected.
> JMS_BODY_FIELD:JMSText = <Message Body>



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message