Issue Details (XML | Word | Printable)

Key: AMQ-978
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Hiram Chirino
Reporter: Sileshi Kassa
Votes: 0
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
ActiveMQ

No Messaged delivery when mixing Perl stomp client Producer/Consumer and Java JMS Producer/Consumer

Created: 15/Oct/06 11:49 AM   Updated: 25/Oct/06 01:40 PM
Return to search
Component/s: Connector
Affects Version/s: None
Fix Version/s: 4.0.2, 4.1.0

Time Tracking:
Not Specified

File Attachments:
  Size
Text File Licensed for inclusion in ASF works Net-Stomp-0.31-bytemessage-support.patch 2006-10-19 09:53 PM Hiram Chirino 3 kB
File Licensed for inclusion in ASF works Net-Stomp-0.31-bytemessage-support.sileshi-patch 2006-10-23 02:06 PM Sileshi Kassa 4 kB
Text File Publisher.pl 2006-10-15 11:49 AM Sileshi Kassa 1 kB
Text File Subscriber.pl 2006-10-15 11:49 AM Sileshi Kassa 1.0 kB
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


 Description  « Hide
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 as
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.



 All   Comments   Work Log   Change History   Subversion Commits   FishEye   Crucible      Sort Order: Ascending order - Click to sort in descending order
No related commits found.