Bug AMQ-978:No message exchange between Java JMS and Perl Stomp clients

[sileshi]

I have recently discovered a problem with ActiveMQ when attempting to
exchange messages between Java JMS and Perl Stomp clients. No Message
gets delivered from one side to the other.

According to James Strachan of ActiveMQ team, there is no architectural/design
limitation to do those sort of message sending. He said that there is no
difference between a message sent by Stomp, JMS, REST, or Ajax. Thus, a
messge sent from any of the connector's clients, should be delievered to
any  destination consumer. This is very reassuring.

I have opened a bug report AMQ-978. I will ask other users if they run
into similar problem either Perl Stomp - Java JMS, or any other combination,
please update this thread with info.

-Sileshi

[chirino]

Have you tried it against a 4.0.1 or 4.0.2-SNAPSHOT
4.0 had some known STOMP problems.

On 10/18/06, sileshi <[hidden email]> wrote:

>
>
> I have recently discovered a problem with ActiveMQ when attempting to
> exchange messages between Java JMS and Perl Stomp clients. No Message
> gets delivered from one side to the other.
>
> According to James Strachan of ActiveMQ team, there is no
> architectural/design
> limitation to do those sort of message sending. He said that there is no
> difference between a message sent by Stomp, JMS, REST, or Ajax. Thus, a
> messge sent from any of the connector's clients, should be delievered to
> any  destination consumer. This is very reassuring.
>
> I have opened a bug report AMQ-978. I will ask other users if they run
> into similar problem either Perl Stomp - Java JMS, or any other
> combination,
> please update this thread with info.
>
> -Sileshi
> --
> View this message in context:
> http://www.nabble.com/Bug-AMQ-978%3ANo-message-exchange-between-Java-JMS-and-Perl-Stomp-clients-tf2467960.html#a6880693
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>

--
Regards,
Hiram

Blog: http://hiramchirino.com

[sileshi]

I now know the reason why Java JMS client message I was sending to
Perl Stomp client did not get to Perl side. The reason is the Java JMS
client sending Bytes message and The Net::Stomp module's receive_frame()
could not read the socket. Everytime it reads zero length bytes.

But if I sent Text message from the JMS client, no problem.

Hiram Chirino wrote

Have you tried it against a 4.0.1 or 4.0.2-SNAPSHOT
4.0 had some known STOMP problems.

On 10/18/06, sileshi <[e-mail]> wrote:
>
>
> I have recently discovered a problem with ActiveMQ when attempting to
> exchange messages between Java JMS and Perl Stomp clients. No Message
> gets delivered from one side to the other.
>
> According to James Strachan of ActiveMQ team, there is no
> architectural/design
> limitation to do those sort of message sending. He said that there is no
> difference between a message sent by Stomp, JMS, REST, or Ajax. Thus, a
> messge sent from any of the connector's clients, should be delievered to
> any  destination consumer. This is very reassuring.
>
> I have opened a bug report AMQ-978. I will ask other users if they run
> into similar problem either Perl Stomp - Java JMS, or any other
> combination,
> please update this thread with info.
>
> -Sileshi
> --
> View this message in context:
> http://www.nabble.com/Bug-AMQ-978%3ANo-message-exchange-between-Java-JMS-and-Perl-Stomp-clients-tf2467960.html#a6880693
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>


--
Regards,
Hiram

Blog: http://hiramchirino.com

[sileshi]

I'm still using 4.0. Is 4.0.2 stable? or should I try
4.0.1?

-Sileshi

Hiram Chirino wrote

Have you tried it against a 4.0.1 or 4.0.2-SNAPSHOT
4.0 had some known STOMP problems.

On 10/18/06, sileshi <[e-mail]> wrote:
>
>
> I have recently discovered a problem with ActiveMQ when attempting to
> exchange messages between Java JMS and Perl Stomp clients. No Message
> gets delivered from one side to the other.
>
> According to James Strachan of ActiveMQ team, there is no
> architectural/design
> limitation to do those sort of message sending. He said that there is no
> difference between a message sent by Stomp, JMS, REST, or Ajax. Thus, a
> messge sent from any of the connector's clients, should be delievered to
> any  destination consumer. This is very reassuring.
>
> I have opened a bug report AMQ-978. I will ask other users if they run
> into similar problem either Perl Stomp - Java JMS, or any other
> combination,
> please update this thread with info.
>
> -Sileshi
> --
> View this message in context:
> http://www.nabble.com/Bug-AMQ-978%3ANo-message-exchange-between-Java-JMS-and-Perl-Stomp-clients-tf2467960.html#a6880693
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>


--
Regards,
Hiram

Blog: http://hiramchirino.com

[James Strachan-2]

Yes 4.0.2 is stable; though won't have the official release until next
week. I'd recommend moving to 4.0.2 ASAP as its got lots of bug fixes,
4.0.1 is the next best thing.

Note that the 4.0.x releases only contain bug fixes.


On 10/19/06, sileshi <[hidden email]> wrote:

>
> I'm still using 4.0. Is 4.0.2 stable? or should I try
> 4.0.1?
>
> -Sileshi
>
> Hiram Chirino wrote:
> >
> > Have you tried it against a 4.0.1 or 4.0.2-SNAPSHOT
> > 4.0 had some known STOMP problems.
> >
> > On 10/18/06, sileshi <[hidden email]> wrote:
> >>
> >>
> >> I have recently discovered a problem with ActiveMQ when attempting to
> >> exchange messages between Java JMS and Perl Stomp clients. No Message
> >> gets delivered from one side to the other.
> >>
> >> According to James Strachan of ActiveMQ team, there is no
> >> architectural/design
> >> limitation to do those sort of message sending. He said that there is no
> >> difference between a message sent by Stomp, JMS, REST, or Ajax. Thus, a
> >> messge sent from any of the connector's clients, should be delievered to
> >> any  destination consumer. This is very reassuring.
> >>
> >> I have opened a bug report AMQ-978. I will ask other users if they run
> >> into similar problem either Perl Stomp - Java JMS, or any other
> >> combination,
> >> please update this thread with info.
> >>
> >> -Sileshi
> >> --
> >> View this message in context:
> >> http://www.nabble.com/Bug-AMQ-978%3ANo-message-exchange-between-Java-JMS-and-Perl-Stomp-clients-tf2467960.html#a6880693
> >> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
> >>
> >>
> >
> >
> > --
> > Regards,
> > Hiram
> >
> > Blog: http://hiramchirino.com
> >
> >
>
> --
> View this message in context: http://www.nabble.com/Bug-AMQ-978%3ANo-message-exchange-between-Java-JMS-and-Perl-Stomp-clients-tf2467960.html#a6897789
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>

--

James
-------
http://radio.weblogs.com/0112098/

[sileshi]

I did some research dealing with Perl-Java clients interaction
via Bytes Message and here is a link:
http://www.nabble.com/AMQ-Missing-JMS-Bytes-Message-on-stomp-tf2483639.html

sileshi wrote

I now know the reason why Java JMS client message I was sending to
Perl Stomp client did not get to Perl side. The reason is the Java JMS
client sending Bytes message and The Net::Stomp module's receive_frame()
could not read the socket. Everytime it reads zero length bytes.

But if I sent Text message from the JMS client, no problem.

Hiram Chirino wrote

Have you tried it against a 4.0.1 or 4.0.2-SNAPSHOT
4.0 had some known STOMP problems.

On 10/18/06, sileshi <[e-mail]> wrote:
>
>
> I have recently discovered a problem with ActiveMQ when attempting to
> exchange messages between Java JMS and Perl Stomp clients. No Message
> gets delivered from one side to the other.
>
> According to James Strachan of ActiveMQ team, there is no
> architectural/design
> limitation to do those sort of message sending. He said that there is no
> difference between a message sent by Stomp, JMS, REST, or Ajax. Thus, a
> messge sent from any of the connector's clients, should be delievered to
> any  destination consumer. This is very reassuring.
>
> I have opened a bug report AMQ-978. I will ask other users if they run
> into similar problem either Perl Stomp - Java JMS, or any other
> combination,
> please update this thread with info.
>
> -Sileshi
> --
> View this message in context:
> http://www.nabble.com/Bug-AMQ-978%3ANo-message-exchange-between-Java-JMS-and-Perl-Stomp-clients-tf2467960.html#a6880693
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>


--
Regards,
Hiram

Blog: http://hiramchirino.com

[sileshi]

James.Strachan wrote

>Yes 4.0.2 is stable; though won't have the official release until next
>week. I'd recommend moving to 4.0.2 ASAP as its got lots of bug fixes,
>4.0.1 is the next best thing.
>
>Note that the 4.0.x releases only contain bug fixes.

I have tried 4.0.1, that does not seem to fix the Java JMS Bytes Message
sending to Perl Stomp client. I'm also unable to build latest 4.1 SNAPSHOT
due to people.apache.org has been down last three days.

Thus, I have tried to test with 4.1 SNAPSHOT from Oct. 11/2006, and
this doesn't seem to fix the problem.

I get socket read problem of reading a single newline byte followed
by zero byte read.

But all other combinations of text/binary and Java JMS/Perl Stomp clients
works fine on 4.0, 4.0.1 and 4.1(Oct. 11/06 SNAPSHOT).

I will wait until people.apache.org is up and build 4.1.

Regards,
Sileshi


On 10/19/06, sileshi <[e-mail]> wrote:
>
> I'm still using 4.0. Is 4.0.2 stable? or should I try
> 4.0.1?
>
> -Sileshi
>
> Hiram Chirino wrote:
> >
> > Have you tried it against a 4.0.1 or 4.0.2-SNAPSHOT
> > 4.0 had some known STOMP problems.
> >
> > On 10/18/06, sileshi <[e-mail]> wrote:
> >>
> >>
> >> I have recently discovered a problem with ActiveMQ when attempting to
> >> exchange messages between Java JMS and Perl Stomp clients. No Message
> >> gets delivered from one side to the other.
> >>
> >> According to James Strachan of ActiveMQ team, there is no
> >> architectural/design
> >> limitation to do those sort of message sending. He said that there is no
> >> difference between a message sent by Stomp, JMS, REST, or Ajax. Thus, a
> >> messge sent from any of the connector's clients, should be delievered to
> >> any  destination consumer. This is very reassuring.
> >>
> >> I have opened a bug report AMQ-978. I will ask other users if they run
> >> into similar problem either Perl Stomp - Java JMS, or any other
> >> combination,
> >> please update this thread with info.
> >>
> >> -Sileshi
> >> --
> >> View this message in context:
> >> http://www.nabble.com/Bug-AMQ-978%3ANo-message-exchange-between-Java-JMS-and-Perl-Stomp-clients-tf2467960.html#a6880693
> >> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
> >>
> >>
> >
> >
> > --
> > Regards,
> > Hiram
> >
> > Blog: http://hiramchirino.com
> >
> >
>
> --
> View this message in context: http://www.nabble.com/Bug-AMQ-978%3ANo-message-exchange-between-Java-JMS-and-Perl-Stomp-clients-tf2467960.html#a6897789
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>


--

James
-------
http://radio.weblogs.com/0112098/

[sileshi]

The only remaining problem with Java JMS client sending Bytes Messages
to perl Stomp client is now fixed in ActiveMQ 4.1 SNAPSHOT I have built.
I have started with quite a few problems two weeks ago, and now
it looks good.

Many thanks for those who helped,  James and Hiram specially.
You guys are wornderful people to work with.

Regards,
Sileshi

sileshi wrote

I did some research dealing with Perl-Java clients interaction
via Bytes Message and here is a link:
http://www.nabble.com/AMQ-Missing-JMS-Bytes-Message-on-stomp-tf2483639.html

sileshi wrote

I now know the reason why Java JMS client message I was sending to
Perl Stomp client did not get to Perl side. The reason is the Java JMS
client sending Bytes message and The Net::Stomp module's receive_frame()
could not read the socket. Everytime it reads zero length bytes.

But if I sent Text message from the JMS client, no problem.

Hiram Chirino wrote

Have you tried it against a 4.0.1 or 4.0.2-SNAPSHOT
4.0 had some known STOMP problems.

On 10/18/06, sileshi <[e-mail]> wrote:
>
>
> I have recently discovered a problem with ActiveMQ when attempting to
> exchange messages between Java JMS and Perl Stomp clients. No Message
> gets delivered from one side to the other.
>
> According to James Strachan of ActiveMQ team, there is no
> architectural/design
> limitation to do those sort of message sending. He said that there is no
> difference between a message sent by Stomp, JMS, REST, or Ajax. Thus, a
> messge sent from any of the connector's clients, should be delievered to
> any  destination consumer. This is very reassuring.
>
> I have opened a bug report AMQ-978. I will ask other users if they run
> into similar problem either Perl Stomp - Java JMS, or any other
> combination,
> please update this thread with info.
>
> -Sileshi
> --
> View this message in context:
> http://www.nabble.com/Bug-AMQ-978%3ANo-message-exchange-between-Java-JMS-and-Perl-Stomp-clients-tf2467960.html#a6880693
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>


--
Regards,
Hiram

Blog: http://hiramchirino.com