You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Marnie McCormack (JIRA)" <qp...@incubator.apache.org> on 2006/12/12 14:04:21 UTC

[jira] Updated: (QPID-139) consume with Mule gives NullPointerException in FieldTableKeyEnumeration

     [ http://issues.apache.org/jira/browse/QPID-139?page=all ]

Marnie McCormack updated QPID-139:
----------------------------------


Unit tests added to exercise code and user confirmation that bug resolved.

> consume with Mule gives NullPointerException in FieldTableKeyEnumeration
> ------------------------------------------------------------------------
>
>                 Key: QPID-139
>                 URL: http://issues.apache.org/jira/browse/QPID-139
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Client
>    Affects Versions: M1
>         Environment: Windows XP Pro SP1
> Mule 1.3.2
>            Reporter: Aaron Bell
>         Assigned To: Marnie McCormack
>             Fix For: M2
>
>         Attachments: mule-qpid-test-minimal.zip, mule_test.log
>
>
> Mule can write to Qpid queues successfully. Reading from Qpid seems to produce a NPE in the client.
> 1. start M1 Qpid broker
> 2. write a message to "direct://amq.direct//queue" using a JMS tool
> 3. confirm MessageCount is 1 using jconsole
> 4. launch Mule with simple config reading from queue
> 5. Mule fails as below
> 6. MessageCount drops to zero, ActiveConsumerCount stays at 1
> Log shows [excerpt]:
> Root Exception stack trace:
> java.lang.NullPointerException
> 	at org.apache.qpid.framing.FieldTableKeyEnumeration.<init>(FieldTableKeyEnumeration.java:35)
> 	at org.apache.qpid.client.message.AbstractJMSMessage$1.<init>(AbstractJMSMessage.java:436)
> 	at org.apache.qpid.client.message.AbstractJMSMessage.getPropertyNames(AbstractJMSMessage.java:434)
> 	at org.mule.providers.jms.JmsMessageAdapter.setMessage(JmsMessageAdapter.java:225)
> 	at org.mule.providers.jms.JmsMessageAdapter.<init>(JmsMessageAdapter.java:44)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira