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.