You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Robbie Gemmell (Jira)" <ji...@apache.org> on 2020/08/07 15:00:00 UTC
[jira] [Commented] (PROTON-2256) msg.content_type is null when
reading from aws mq.
[ https://issues.apache.org/jira/browse/PROTON-2256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17173186#comment-17173186 ]
Robbie Gemmell commented on PROTON-2256:
----------------------------------------
This is very likely not an issue in proton, but in the broker and/or how it/you are sending the messages.
The message 'content_type' property comes from the specific content-type field in the AMQP message 'properties' section. If its empty, you wont get one.
The screenshot is on the other hand probably showing general broker metdata, or 'message properties' which are stored in the quite separate AMQP message 'application properties' section.
> msg.content_type is null when reading from aws mq.
> --------------------------------------------------
>
> Key: PROTON-2256
> URL: https://issues.apache.org/jira/browse/PROTON-2256
> Project: Qpid Proton
> Issue Type: Test
> Reporter: Angelo Mendonca
> Priority: Major
> Attachments: image-2020-08-06-12-21-25-014.png
>
>
> The message content_type is application/json but when we receive the message from the queue using a BlockingConnection we get none.
>
> !image-2020-08-06-12-21-25-014.png|width=203,height=74!
> is what we see for that message in the activemq console.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org