Mailing-List: contact activemq-dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: activemq-dev@geronimo.apache.org
Received-SPF: pass (asf.osuosl.org: domain of chirino@gmail.com designates
 64.233.162.204 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=q+XSO0rimCdgwW6sd6tk3GqGkadz57KkAb1C6lAHrte0BWouDIRy+zHlYDZWFb1D4Q+GSD+H6bocJL7eBcrvAsHxZFT7bdAVlQnZHZMcVfnolEtB8VZjc67RQMGn9EVDAlR1g/GH9BRaiBwbdD+1wpGuLdJK3saMNdIv/ecXkTQ=
Message-ID: <af2843cd0604111541i2fac2886m6a8972b2507566e6@mail.gmail.com>
Date: Tue, 11 Apr 2006 18:41:11 -0400
From: "Hiram Chirino" <hiram@hiramchirino.com>
Sender: chirino@gmail.com
To: activemq-dev@geronimo.apache.org
Subject: Re: STOMP bytes messages
In-Reply-To: <8a6feb940604111434g437d385o3d9bc164a0690de4@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <8a6feb940604111434g437d385o3d9bc164a0690de4@mail.gmail.com>

I'd be happy to try to debug this with you. What should I build and
run to get your test case going?

On 4/11/06, Nathan Mittler <nathan.mittler@gmail.com> wrote:
> I'm trying to upgrade CMS to work property with bytes messages.  I assume
> that a bytes message in stomp is simply a message that has a
> "content-length" header, defining the size of the body.  My test is a
> modification of the example in CMS, where I have a stomp publisher and st=
omp
> subscriber through the same connection.  The publisher sends the message =
and
> the subscriber should receive it (a sleep is done after the publish to
> facilitate the receipt of the message).  This works fine for text message=
s,
> but not so much with the bytes message.  I have logged the exact data tha=
t
> I'm writing to the socket below (non-printable characters are in brackets=
 to
> show their decimal value).
>
> SEND[10]content-length:10[10]destination:/topic/mytopic[10][10][0][1][2][=
3][0][4][5][6][0][0][0]
>
> So the content-length is 10 and data it contains is: 0,1,2,3,0,4,5,6,0,0 =
...
> the extra null at the end is required by stomp to denote the end of the
> frame.  So I send this out (without any indication of a problem) and it
> seems that I get something in on the socket, but when I read, there is
> nothing there - indicating a broken socket.  If I switch the code back to
> using text messages, everything is happy.
>
> Any ideas?
>
> Thanks,
> Nate
>
>


--
Regards,
Hiram