You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Jakub Scholz (JIRA)" <ji...@apache.org> on 2015/05/14 14:35:59 UTC

[jira] [Created] (QPIDJMS-49) Not all messages can be received by the Qpid JMS client

Jakub Scholz created QPIDJMS-49:
-----------------------------------

             Summary: Not all messages can be received by the Qpid JMS client
                 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


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