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

William MacDonald commented on AMQ-725:
---------------------------------------

I have tested this with the new 4.01 release of ActiveMQ using the default 
configuration file and I am still having the problem.

After performing a TCP connections to the Broker on the listener defined as 
tcp://wrpkmnb:61613?wireFormat=stomp:

I transmit the connection message:

CONNECT\010login:billm\010passcode:billm\010client-id:webProcessor\010\010\000

After which I receive the message:

CONNECTED\010session:webProcessor\010\010\000\010

I then try to subscribe to a queue:

SUBSCRIBE\010destination:/queue/WebRequest\010id:webProcessorconsumer:2\010ack:client\010activemq.prefetchSize:1\010\010\000

And no response is returned from the Broker but the log shows the following 
message.

Exception in thread "ActiveMQ Connection Dispatcher: 28939486" 
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)

For readability I have replaced the linefeeds with \010 and the nulls with \000 
representations.

> 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.1, 4.0.2

>
>
> 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

Reply via email to