activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hiram Chirino" <hi...@hiramchirino.com>
Subject Re: message is truncated at \0 ?
Date Thu, 20 Dec 2007 22:40:23 GMT
Per http://stomp.codehaus.org/Protocol

"It is recommended that SEND frames include a content-length header
which is a byte count for the length of the message body. If a
content-length header is included, this number of bytes should be
read, regardless of whether or not there are null characters in the
body. The frame still needs to be terminated with a null byte and if a
content-length is not specified, the first null byte encountered
signals the end of the frame."

On Dec 19, 2007 1:36 PM, amaas <amaas@proofpoint.com> wrote:
>
> I was using activemq rc3 and found that if I send binary data (via stomp)
> that contain null (\0), the msg will be trucated at \0 location. And further
> submission (or maybe fetching) won't work any more until I restarted
> activemq
>
> My question is if activemq does have the constraint on binary data (in
> general) or one with \0 specifically.
>
> thank you.
> --
> View this message in context: http://www.nabble.com/message-is-truncated-at-%5C0---tp14422619s2354p14422619.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>



-- 
Regards,
Hiram

Blog: http://hiramchirino.com

Open Source SOA
http://open.iona.com

Mime
View raw message