activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hiram Chirino (JIRA)" <>
Subject [jira] Resolved: (AMQ-725) Messages Sent by JMS that contain header properties cause error when STOMP client registers a Subscriber
Date Sun, 02 Jul 2006 17:00:51 GMT
     [ ]
Hiram Chirino resolved AMQ-725:

    Fix Version:     (was: 4.0.2)
     Resolution: Fixed

I just tested against 4.1-SNAPSHOT and this is working.

> Messages Sent by JMS that contain header properties cause error when STOMP client registers
a Subscriber
> --------------------------------------------------------------------------------------------------------
>          Key: AMQ-725
>          URL:
>      Project: ActiveMQ
>         Type: Bug

>   Components: Transport
>     Versions: 4.0
>  Environment: Running on WinXP with Sun JDK1.5.0_06
>     Reporter: William MacDonald
>     Assignee: Hiram Chirino
>     Priority: Blocker
>      Fix For: 4.1

> I am using the lastest 4.0 release build of ActiveMQ and I have been trying to produce
messages in a JMS client and receive the messages in a STOMP client.
> What I have found is that if the JMS Client adds header properties to the message to
be delivered to ActiveMQ then when I subscribe with the STOMP client I am receiving the Error
listed below.  If I remove all header properties then the message is transmitted correctly.
 I have also found that if I send messages with a STOMP client that has header properties
then everything works correctly.
> java.lang.NullPointerException
> at java.util.Hashtable.put(Unknown Source)
> at java.util.Hashtable.putAll(Unknown Source)
> at org.apache.activemq.transport.stomp.FrameBuilder.addHeaders(
> at org.apache.activemq.transport.stomp.Subscription.receive(
> at org.apache.activemq.transport.stomp.StompWireFormat.writeCommand(
> at org.apache.activemq.transport.stomp.StompWireFormat.marshal(
> at org.apache.activemq.transport.tcp.TcpTransport.oneway(
> at org.apache.activemq.transport.InactivityMonitor.oneway(
> at org.apache.activemq.transport.MutexTransport.oneway(
> at org.apache.activemq.transport.ResponseCorrelator.oneway(
> at
> at
> at
> at org.apache.activemq.thread.DedicatedTaskRunner.runTask(
> at org.apache.activemq.thread.DedicatedTaskRunner.access$000(
> at org.apache.activemq.thread.DedicatedTaskRunner$

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message