[jira] Updated: (QPID-1374) Java client throws NullPointerException when header " message properties" is not set

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[jira] Updated: (QPID-1374) Java client throws NullPointerException when header " message properties" is not set

JIRA qpid-dev@incubator.apache.org

     [ https://issues.apache.org/jira/browse/QPID-1374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marnie McCormack updated QPID-1374:
-----------------------------------

    Fix Version/s: M5
         Assignee: Aidan Skinner  (was: Rafael H. Schloming)

> 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: Aidan Skinner
>             Fix For: M5
>
>
> 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.

Loading...