[
https://issues.apache.org/jira/browse/QPID-1374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12643051#action_12643051
]
Rafael H. Schloming commented on QPID-1374:
-------------------------------------------
The fix for this isn't safe. (Nor is the original code for this safe.) There is
no guarantee that the headers will be delivered in a particular order or that
if only one header Struct is delivered it is the delivery properties header
struct.
We should really not use a Struct[] at all. The code in MessageFactoryRegistry
pulls out the MessageProperties correctly. It could simply pass them in
directly or pass in the whole Header or the MessageTransfer object to the
AbstractJMSMessageFactory and allow the appropriate accessors to be used there.
> Java client throws NullPointerException when header " message properties"
> is not set
> ---------------------------------------------------------------------------------------
>
> Key: QPID-1374
> URL: https://issues.apache.org/jira/browse/QPID-1374
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Affects Versions: M4
> Reporter: Arnaud Simon
> Assignee: Arnaud Simon
> Fix For: M4
>
>
> The java JMS layer expects that all messages have message properties set.
> This is however not always the case as AMQP doesn't mandate the message
> properties header to always be set. For example the python client doesn't set
> the message properties when they are empty.
> How to reproduce:
> - Send messages using the python client
> - Consume those messages with a java consumer
> Solution:
> update AbstractJMSMessageFactory and MessageFactoryRegistry for dealing with
> null message properties header
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
