[
https://issues.apache.org/jira/browse/QPID-1374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rob Godfrey updated QPID-1374:
------------------------------
Fix Version/s: (was: M4)
AFAICT there have been no changes to this class since the changes described
here which are (as Rafi points out) unsafe, but no more so than the previous
code.
Therefore I propose we descope from M4 and fix in M5 or some other coming
release.
> 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: Rafael H. Schloming
>
> 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.
