You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Rafael H. Schloming (JIRA)" <qp...@incubator.apache.org> on 2009/02/19 19:08:02 UTC

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

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

Rafael H. Schloming closed QPID-1374.
-------------------------------------


I've reviewed the change and the issue I mentioned is fixed.

> 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: Rajith Attapattu
>             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.


---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org