activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (AMQCPP-476) Reading of Stomp Frame with content length may throw excecption
Date Wed, 01 May 2013 22:22:20 GMT

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

Timothy Bish resolved AMQCPP-476.
---------------------------------

       Resolution: Fixed
    Fix Version/s: 3.7.0

I added your tests and didn't see any failures against ActiveMQ.  However I did make a change
anyway to StompFrame similar to you patch expect that I just used the DataInputStream's readFully
method to ensure all the data gets pulled off the wire. 
                
> Reading of Stomp Frame with content length may throw excecption
> ---------------------------------------------------------------
>
>                 Key: AMQCPP-476
>                 URL: https://issues.apache.org/jira/browse/AMQCPP-476
>             Project: ActiveMQ C++ Client
>          Issue Type: Bug
>          Components: Stomp
>    Affects Versions: 3.6.0
>         Environment: Solaris 10
> Apollo
> AMQ
>            Reporter: Jeremy Leung
>            Assignee: Timothy Bish
>             Fix For: 3.7.0
>
>         Attachments: consumer.cpp, Publisher.java, StompFrame.cpp.patch.txt, unit_test.txt
>
>
> -- HOW TO REPRODUCE --
> 1) Setup a consumer to listen for messages on Topic XXX using CMS with stomp.
> 2) Setup a publisher to send a messages from java JMS interface to Topic XXX continually.
(with org.fusesource.stomp.jms.*)
> 3) An exception is thrown in consumer from StompWireFormat::readStompBody() with description
"Read Content Length, and no trailing null"
> -- BLOCK DIAGRAM --
> All components are in different hosts and all run under Solaris 10 environment.
> | C++ CONSUMER | <- | APOLLO 1.6 / AMQ 5.4.2 | <- | JAVA PUBLISHER |
> or
> | C++ CONSUMER | <- | APOLLO 1.6 / AMQ 5.4.2 | <- | C++ PUBLISHER |

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message