Let's say that I have a cluster (for high availability) where each server
listens to another system's multicasted messages. Obviously, each message
from the other system would be received multiple times (once by each server
in a cluster). If I wanted to direct the messages to ActiveMQ, would ther
OK, mystery solved:)
I forgot to mentioned that I am *NOT* using any of the standard AMQ Ajax
adapters that come with ActiveMQ distribution. As I am experimenting with
Sencha Touch, I created a Sencha Touch adapter by looking at how the jQuery
one is implemented. It turned out that the adapter wa
Update: HTTP request/response, as reported by Safari's Web Inspector:
1. Initial addListener() call:
--
Request URL:http://localhost:8161/amq/amq
Request Method:POST
Status Code:200 OK
Request Headers
Cache-Control:max-age=0
Content-Type:application/x-www-form-urlencoded;
First, my javascript code:
var queue = 'queue://qTest';
amq.init({ uri: 'http://localhost:8161/amq/amq', logging: true, timeout: 45,
clientId:(new Date()).getTime().toString() });
amq.addListener('testMq', queue, handler);
After this, I have no issues with sending messages to any queue
Stomp.js is a javascript used in the communications via websocket so it
doesn't affect the communication via Ajax i posted before ( i cut the part
of websocket code )
I modified the amq.js code following the patch indications but the problem
still remains unsolved :(
Tried to refresh the page bu
Consider the "Send a JMS Message" page of the web console:
http://localhost:8161/admin/send.jsp
Is there documentation that describes exactly what the purposes/goals are of
the following fields:
delay(ms)
Time(ms) to wait before scheduling again
Number of repeats
Use a CRON string for scheduling
