activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sileshi Kassa (JIRA)" <>
Subject [jira] Commented: (AMQ-978) No Messaged delivery when mixing Perl stomp client Producer/Consumer and Java JMS Producer/Consumer
Date Thu, 19 Oct 2006 13:52:16 GMT
    [ ] 
Sileshi Kassa commented on AMQ-978:

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 receiving it
on the Perl side.

This seems to be more of the Net::Stomp package problem
with binary data which I need to debug and file report.

Therefore, we need to close this bug report as invalid.

> No Messaged delivery when mixing Perl stomp client Producer/Consumer and Java JMS Producer/Consumer
> ---------------------------------------------------------------------------------------------------
>                 Key: AMQ-978
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Connector
>         Environment: This problem seems platform independent: It happens in Linux, Mac
OSX, and Windows.
> Software Used: ActiveMQ 4.0, Java 5.0, JMS, Perl 5.8.7, Perl CPAN module Net-Stomp-0.31
>            Reporter: Sileshi Kassa
>         Attachments:,
> Facts: Perl Stomp client Producer and Consumer works fine
>            Java JMS client Producer and Consumer works fine
> I have also used other Perl Stomp protocol implementation with no problem.
> The problem happens when I mix Java and Perl clients
> Scenario Test 1:
> A. Perl Stomp client Consumer
> B. Java JMS client Producer
> Scenario Test 2:
> A. Java JMS client Consumer
> B. Perl Stomp client Producer
> I have looked into it via Java JMX management jconsole, and it seems to me there is a
wall between
> the stomp server and default server. It the stomp server only passes messages coming
from stomp lients
> and default server also does the same.
> If this is truly the case, and this is by design, I will be very disappointed. There
should not be any wall.
> A message is message irrespective of its source and should be delivered to any one that
is listening
> on the same destination.
> I will attach the Perl clients testcases.
> For Java client,  a simple JMS client Producer and Consumer with the same topic used
> the perl side will do the job. The topic I used on the perl side: "/topic/Test.CrossDelivery"
> and the Java side topic is  "Test.CrossDelivery"
> This problem is a show stopper for us.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message