Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Message-ID: <10849112.1193082983474.JavaMail.jira@brutus>
Date: Mon, 22 Oct 2007 12:56:23 -0700 (PDT)
From: "Hiram Chirino (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Subject: [jira] Resolved: (AMQ-670) STOMP not setting content-length on byte
 messages.
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit


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

Hiram Chirino resolved AMQ-670.
-------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 4.0 RC2)
                   5.0.0

I used the attached send.rb and recv.rb script to test sending a receiving a message with the content-length header set and it seem to work fine against the activemq trunk.

Closing issue out again as fixed on 5.0

> STOMP not setting content-length on byte messages.
> --------------------------------------------------
>
>                 Key: AMQ-670
>                 URL: https://issues.apache.org/activemq/browse/AMQ-670
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Transport
>            Reporter: Hiram Chirino
>            Assignee: Hiram Chirino
>             Fix For: 5.0.0
>
>         Attachments: recv.rb, send.rb
>
>
> It was also setting the content-length as a propertly on the JMS message when receiving a binary message.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.