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 <[EMAIL PROTECTED]> 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#a6897020 Sent from the ActiveMQ - User mailing list archive at Nabble.com.
