[jira] Assigned: (AMQ-725) Messages Sent by JMS that contain header properties cause error when STOMP client registers a Subscriber

["Hiram Chirino (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/activemq/browse/AMQ-725?page=all ]

Hiram Chirino reassigned AMQ-725:
---------------------------------

    Assign To: Hiram Chirino

> Messages Sent by JMS that contain header properties cause error when STOMP client registers a Subscriber
> --------------------------------------------------------------------------------------------------------
>
>          Key: AMQ-725
>          URL: https://issues.apache.org/activemq/browse/AMQ-725
>      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.0.1, 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(FrameBuilder.java:65)
> at org.apache.activemq.transport.stomp.Subscription.receive(Subscription.java:76)
> at org.apache.activemq.transport.stomp.StompWireFormat.writeCommand(StompWireFormat.java:154)
> at org.apache.activemq.transport.stomp.StompWireFormat.marshal(StompWireFormat.java:305)
> at org.apache.activemq.transport.tcp.TcpTransport.oneway(TcpTransport.java:124)
> at org.apache.activemq.transport.InactivityMonitor.oneway(InactivityMonitor.java:141)
> at org.apache.activemq.transport.MutexTransport.oneway(MutexTransport.java:44)
> at org.apache.activemq.transport.ResponseCorrelator.oneway(ResponseCorrelator.java:60)
> at org.apache.activemq.broker.TransportConnection.dispatch(TransportConnection.java:211)
> at org.apache.activemq.broker.AbstractConnection.processDispatch(AbstractConnection.java:581)
> at org.apache.activemq.broker.AbstractConnection.iterate(AbstractConnection.java:597)
> at org.apache.activemq.thread.DedicatedTaskRunner.runTask(DedicatedTaskRunner.java:87)
> at org.apache.activemq.thread.DedicatedTaskRunner.access$000(DedicatedTaskRunner.java:24)
> at org.apache.activemq.thread.DedicatedTaskRunner$1.run(DedicatedTaskRunner.java:38)

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