[AMQNET-167] Stomp Transport encodes trailling double byte null

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.0.0
• Fix Version/s: 1.1.0
• Assignee: Timothy A. Bish
• Reporter: Timothy A. Bish
• Created: 25/Jun/09 14:41
• Updated: 09/Jul/09 00:43
• Resolved: 25/Jun/09 15:29

Description

When appending the trailing null to a Stomp Frame the Stomp Transport's StompFrameStream is adding a multibyte char null instead of a single byte null which is the correct terminator as per the Stomp spec.

Reported By: matt walsh on the mailing list with supplied fix.