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 2017/09/27 11:48:00 UTC
[jira] [Commented] (QPIDJMS-295) AMQP property content-encoding
cannot be retrieved via JMS_AMQP_ContentEncoding
[ https://issues.apache.org/jira/browse/QPIDJMS-295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16182422#comment-16182422 ]
Robbie Gemmell commented on QPIDJMS-295:
----------------------------------------
JMS_AMQP_ContentEncoding is an ActiveMQ-specific extension, using an Application Property which the broker internally utilises when doing certain things such as converting messages between different protocols when using some of its 'transformers'. The broker itself will presumably be stripping that Application Property (itself a spec violation) somewhere while doing that given your configuration, giving the resulting behaviour, as the Qpid JMS client does not specifically know about that property and does not map it to the content-encoding field of the AMQP message Properties section (not Application Properties, which is separate).
Finalising behaviour around content type and encoding is an outstanding area of work, its a fairly complicated subject, but really sits entirely outwith JMS functionality.
> 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
>
> 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 JMS
> 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
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org