You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2015/05/15 15:38:01 UTC
[jira] [Commented] (QPIDJMS-49) handle messages with an unknown
content-type
[ https://issues.apache.org/jira/browse/QPIDJMS-49?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14545498#comment-14545498 ]
ASF subversion and git services commented on QPIDJMS-49:
--------------------------------------------------------
Commit 3637ec99936082b377341827813ec2f76333ed2b in qpid-jms's branch refs/heads/master from Robert Gemmell
[ https://git-wip-us.apache.org/repos/asf?p=qpid-jms.git;h=3637ec9 ]
QPIDJMS-49: ensure messages with unknown content-type and Data sections are handled as BytesMessage, and those with no sections are handled as Message
> 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
> Reporter: Jakub Scholz
> Assignee: Robbie Gemmell
>
> 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-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org