[jira] Issue Comment Edited: (AMQNET-60) Sending BytesMessages does not send terminating NULL byte to end frame.

["Jim Gomes (JIRA)" <ji...@apache.org>]

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

semog edited comment on AMQNET-60 at 9/11/07 11:00 AM:
-----------------------------------------------------------

Note: The patch file was generated after applying the patch for [AMQNET-53].  This patch supersedes the fix made to the StompFrameStream.cs file in [AMQNET-53].

      was (Author: semog):
    Note: The patch file was generated after applying the patch for [AMQNET-53].  This patch supersedes the fix for [AMQNET-53].
  
> 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.