[
https://issues.apache.org/jira/browse/QPIDJMS-49?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell resolved QPIDJMS-49.
-----------------------------------
Resolution: Fixed
> handle messages with an unknown content-type
> --------------------------------------------
>
> Key: QPIDJMS-49
> URL: https://issues.apache.org/jira/browse/QPIDJMS-49
> Project: Qpid JMS
> Issue Type: Bug
> Components: qpid-jms-client
> Affects Versions: 0.1.0, 0.2.0
> Reporter: Jakub Scholz
> Assignee: Robbie Gemmell
> Fix For: 0.3.0
>
>
> When a message is received, the client tries to decode the message and
> transform it to JmsMessage. However, the decoding of the message suceeds only
> when the message:
> - has the JMS_MSG_TYPE annotation
> - or has a content type
> - or the content has a specific AMQP type
> However, if the message doesn't match any of these, the client simply returns
> it back to the broker just with a warning:
> 2015-05-14 14:25:53 +0200 WARN org.apache.qpid.jms.provider.amqp.AmqpConsumer
> - Error on transform: Could not create a JMS message from incoming message
> When using the Qpid JMS API with the Qpid C++ broker, it seems to happen
> quite often that the messages falls into this category. For example the
> qpid-send utility (+ other clients based on the C++ API) tends to produce
> this kind of messages.
> Wouldn't it be better to transform such messages to BytesMessages? IMHO a
> client application with some additional knowledge about the message content
> might be able to process the payload correctly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
