Re: STOMP bytes messages
by the way... Stomp, itself, doesn't know the difference between queues and topics. Everything is just a destination. The naming convention used in ActiveMQ's implementation is just that, a naming convention to support on-the-fly creation of things. -Brian On Apr 17, 2006, at 10:44 AM, Mittler, Nathan wrote: Correct. It's currently an incomplete implementation of STOMP - Queues and Transactions are currently missing ... but will be added shortly. Nate -Original Message- From: Dhawan, Vikram (LNG-DAY) [mailto:[EMAIL PROTECTED] Sent: Monday, April 17, 2006 1:42 PM To: activemq-dev@geronimo.apache.org Subject: RE: STOMP bytes messages Nate, This code doesn't support Queues, right? Thanks! Vik -Original Message- From: Mittler, Nathan [mailto:[EMAIL PROTECTED] Sent: Monday, April 17, 2006 12:58 PM To: activemq-dev@geronimo.apache.org Subject: RE: STOMP bytes messages The CMS STOMP client code is here https://svn.apache.org/repos/asf/incubator/activemq/trunk/cms/ I'm currently in the middle of working out a couple of issues (with the help of Hiram), but I'm at work and don't have access to that code at the moment. I should have those fixes posed in a few days or so. Regards, Nate -Original Message- From: Dhawan, Vikram (LNG-DAY) [mailto:[EMAIL PROTECTED] Sent: Monday, April 17, 2006 12:17 PM To: activemq-dev@geronimo.apache.org Subject: RE: STOMP bytes messages Hey Nate, Where can I get latest working code for your CMS client? Thanks! Vik -Original Message- From: Mittler, Nathan [mailto:[EMAIL PROTECTED] Sent: Monday, April 17, 2006 12:10 PM To: activemq-dev@geronimo.apache.org Subject: RE: STOMP bytes messages Great - keep me posted. At this point, I'll be happy just to see data coming back for the bytes message ... no guarantees as to whether the CMS client processes it correctly :) Regards, Nate -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Hiram Chirino Sent: Monday, April 17, 2006 11:45 AM To: activemq-dev@geronimo.apache.org Subject: Re: STOMP bytes messages Hi Nathan, Yep. found a bunch of issues. Next up is trying your c++ client. Regards, Hiram
RE: STOMP bytes messages
Nate, I understand your point; I am open for both of the options most important thing is it should work :-). I really need Queue support with any of the client. Please let me know when you have Queue support in CMS, and I am not sure if oppenwire-cpp is even usable (no one responded to your call). Thanks! Vik -Original Message- From: Mittler, Nathan [mailto:[EMAIL PROTECTED] Sent: Monday, April 17, 2006 1:45 PM To: activemq-dev@geronimo.apache.org Subject: RE: STOMP bytes messages Hi Vik, We're not quite there yet for integrating CMS and Openwire. For now, you just have to pick your poison: CMS (stomp) - or the openwire-cpp client. Regards, Nate -Original Message- From: Dhawan, Vikram (LNG-DAY) [mailto:[EMAIL PROTECTED] Sent: Monday, April 17, 2006 1:36 PM To: activemq-dev@geronimo.apache.org Subject: RE: STOMP bytes messages Thanks Nate, I will try to build it on Solaris and wait for your fixes. I am just wondering where we are maintaining CMS + Openwire integration. Thanks! Vik
Re: STOMP bytes messages
Hiram, I'd found that when I was using bytes messages through STOMP that I was seeing newlines get randomly eaten in the STOMP frame headers, which was breaking my parsing code. I haven't yet gotten around to determining if that was happening inside of ActiveMQ or in my (Python) parsing code. I was also seeing a problem where my binary data was sometimes getting corrupted somehow, such that I ended up just switching to doing a base64 of my data before sending it. Have you seen/fixed anything like those things? - Bruce Hiram Chirino wrote: Yep. found a bunch of issues. Next up is trying your c++ client.
RE: STOMP bytes messages
The CMS STOMP client code is here https://svn.apache.org/repos/asf/incubator/activemq/trunk/cms/ I'm currently in the middle of working out a couple of issues (with the help of Hiram), but I'm at work and don't have access to that code at the moment. I should have those fixes posed in a few days or so. Regards, Nate -Original Message- From: Dhawan, Vikram (LNG-DAY) [mailto:[EMAIL PROTECTED] Sent: Monday, April 17, 2006 12:17 PM To: activemq-dev@geronimo.apache.org Subject: RE: STOMP bytes messages Hey Nate, Where can I get latest working code for your CMS client? Thanks! Vik -Original Message- From: Mittler, Nathan [mailto:[EMAIL PROTECTED] Sent: Monday, April 17, 2006 12:10 PM To: activemq-dev@geronimo.apache.org Subject: RE: STOMP bytes messages Great - keep me posted. At this point, I'll be happy just to see data coming back for the bytes message ... no guarantees as to whether the CMS client processes it correctly :) Regards, Nate -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Hiram Chirino Sent: Monday, April 17, 2006 11:45 AM To: activemq-dev@geronimo.apache.org Subject: Re: STOMP bytes messages Hi Nathan, Yep. found a bunch of issues. Next up is trying your c++ client. Regards, Hiram
Re: STOMP bytes messages
I had tested against the April 6th SNAPSHOT build and had the problem. Have you added code to head since? Regards, Nate On 4/15/06, Hiram Chirino <[EMAIL PROTECTED]> wrote: > > Well, wile working with the Ruby stomp client I found some issues with > the java stuff. I committed some changes that may please try them > out! > >
Re: STOMP bytes messages
Well, wile working with the Ruby stomp client I found some issues with the java stuff. I committed some changes that may please try them out! On 4/14/06, Nathan Mittler <[EMAIL PROTECTED]> wrote: > I just re-read your e-mail and I'm not sure if the issue is the lack of or > the inclusion of an eclipse workspace (oh, the joys of e-mail!). I > extracted the tar and made sure there were eclipse project settings in there > (keep in mind, these files are purely for local builds and will not be > included in any commit to svn). So, I'm not sure if I have any actions :) > > Nate > > On 4/14/06, Mittler, Nathan <[EMAIL PROTECTED]> wrote: > > > > Oops ... sorry about that :). I'm at work right now and don't have > > access to the code - I'll get it to you this evening. > > > > Do you have an eclipse environment with the CDT for building C++ > > projects? ... otherwise I can throw some makefiles together if that's > > easier for you. Unfortunately, the current version of the code only > > works with a pthread environment - hopefully you're not on windoze :). > > > > Nate > > > > -Original Message- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Hiram > > Chirino > > Sent: Friday, April 14, 2006 11:53 AM > > To: activemq-dev@geronimo.apache.org > > Subject: Re: STOMP bytes messages > > > > Howdy.. now eclipse project files were included in the tar :( > > > > On 4/14/06, Hiram Chirino <[EMAIL PROTECTED]> wrote: > > > yep got.. just got a little swamped. Will look into it asap. > > > > > > On 4/14/06, Nathan Mittler <[EMAIL PROTECTED]> wrote: > > > > Hey Hiram, > > > > Just wanted to see if you received the code I sent you (the first > > try was > > > > rejected by the server because of the file size). Let me know if > > you have > > > > any trouble compiling/etc. > > > > > > > > Nate > > > > > > > > > > > > > > > > > -- > > > Regards, > > > Hiram > > > > > > > > > -- > > Regards, > > Hiram > > > > -- Regards, Hiram
Re: STOMP bytes messages
I just re-read your e-mail and I'm not sure if the issue is the lack of or the inclusion of an eclipse workspace (oh, the joys of e-mail!). I extracted the tar and made sure there were eclipse project settings in there (keep in mind, these files are purely for local builds and will not be included in any commit to svn). So, I'm not sure if I have any actions :) Nate On 4/14/06, Mittler, Nathan <[EMAIL PROTECTED]> wrote: > > Oops ... sorry about that :). I'm at work right now and don't have > access to the code - I'll get it to you this evening. > > Do you have an eclipse environment with the CDT for building C++ > projects? ... otherwise I can throw some makefiles together if that's > easier for you. Unfortunately, the current version of the code only > works with a pthread environment - hopefully you're not on windoze :). > > Nate > > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Hiram > Chirino > Sent: Friday, April 14, 2006 11:53 AM > To: activemq-dev@geronimo.apache.org > Subject: Re: STOMP bytes messages > > Howdy.. now eclipse project files were included in the tar :( > > On 4/14/06, Hiram Chirino <[EMAIL PROTECTED]> wrote: > > yep got.. just got a little swamped. Will look into it asap. > > > > On 4/14/06, Nathan Mittler <[EMAIL PROTECTED]> wrote: > > > Hey Hiram, > > > Just wanted to see if you received the code I sent you (the first > try was > > > rejected by the server because of the file size). Let me know if > you have > > > any trouble compiling/etc. > > > > > > Nate > > > > > > > > > > > > -- > > Regards, > > Hiram > > > > > -- > Regards, > Hiram >
Re: STOMP bytes messages
yep got.. just got a little swamped. Will look into it asap. On 4/14/06, Nathan Mittler <[EMAIL PROTECTED]> wrote: > Hey Hiram, > Just wanted to see if you received the code I sent you (the first try was > rejected by the server because of the file size). Let me know if you have > any trouble compiling/etc. > > Nate > > -- Regards, Hiram
Re: STOMP bytes messages
Hey Hiram, Just wanted to see if you received the code I sent you (the first try was rejected by the server because of the file size). Let me know if you have any trouble compiling/etc. Nate
Re: STOMP bytes messages
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 <[EMAIL PROTECTED]> 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 stomp > 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 messages, > but not so much with the bytes message. I have logged the exact data that > 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
STOMP bytes messages
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 stomp 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 messages, but not so much with the bytes message. I have logged the exact data that 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
