Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Message-ID: <14120624.1189533502474.JavaMail.jira@brutus>
Date: Tue, 11 Sep 2007 10:58:22 -0700 (PDT)
From: "Jim Gomes (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Subject: [jira] Updated: (AMQNET-60) Sending BytesMessages does not send
 terminating NULL byte to end frame.
In-Reply-To: <13317176.1189533263195.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit


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

Jim Gomes updated AMQNET-60:
----------------------------

    Attachment: StompFrameStream.cs.patch.txt

> Sending BytesMessages does not send terminating NULL byte to end frame.
> -----------------------------------------------------------------------
>
>                 Key: AMQNET-60
>                 URL: https://issues.apache.org/activemq/browse/AMQNET-60
>             Project: ActiveMQ .Net
>          Issue Type: Bug
>          Components: Stomp
>         Environment: Windows XP SP2
> .NET 2.0
> STOMPConnect 1.0
> TIBCO EMS 4.2.0
>            Reporter: Jim Gomes
>            Assignee: James Strachan
>         Attachments: StompFrameStream.cs.patch.txt
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>
> The {STOMP protocol specification|http://docs.codehaus.org/display/STOMP/Protocol} states that a bytes message frame should still be NULL terminated even when the content-length header is specified. The StompFrameStream.Flush() function does not send this final terminating NULL byte.  This will hang a client that is waiting for a response from the broker, because the broker is waiting for the client to finish sending the frame.

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