qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yufei Cai (Jira)" <j...@apache.org>
Subject [jira] [Commented] (QPIDJMS-295) AMQP property content-encoding cannot be retrieved via JMS_AMQP_ContentEncoding
Date Wed, 06 Nov 2019 12:47:00 GMT

    [ https://issues.apache.org/jira/browse/QPIDJMS-295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16968337#comment-16968337

Yufei Cai commented on QPIDJMS-295:

Content-Encoding is now a formalized AMQP 1.0 property. As such it should be supported for

> AMQP property content-encoding cannot be retrieved via JMS_AMQP_ContentEncoding
> -------------------------------------------------------------------------------
>                 Key: QPIDJMS-295
>                 URL: https://issues.apache.org/jira/browse/QPIDJMS-295
>             Project: Qpid JMS
>          Issue Type: Bug
>          Components: qpid-jms-client
>    Affects Versions: 0.23.0
>            Reporter: Leo Riguspi
>            Priority: Major
> The AMQP property content-encoding can be set but not retrieved:
> 1. Create a message and set the vendor property JMS_AMQP_ContentEncoding=gzip using QPid
> 2. Send the message to an ActiveMQ broker via AMQP 1.0 with transport.transformer=jms
(native does not work!)
> 3. Retrieve the message with QPid JMS: the property JMS_AMQP_ContentEncoding does not
exist anymore in the message and there seem to be no other way of retrieving the content-encoding.

> Note that when consuming the same message with a python client the property seems to
be set and accessible via the message.content_encoding field.

This message was sent by Atlassian Jira

To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org

View raw message