Hi Alikic,
Do you know what exactly made the difference? Is it a specific HTTP
header value or something else that resulted in the consumer getting
dropped? I'm using the amq.js code, but I also see behavior similar to what
you described previously, where after receiving the first batch of mess
Here is the ticket: https://issues.apache.org/jira/browse/AMQ-3117
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Problem-using-Ajax-to-listen-to-a-queue-topic-tp3167287p3187146.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
The adapter depends only on sencha-touch.js. I think it should also work with
plain sencha (not touch), but I didn't test it. Sure, I can post the code.
How do I open a ticket?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Problem-using-Ajax-to-listen-to-a-queue-
On Dec 29, 2010, at 12:13 PM, alikic wrote:
>
> 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 jQ
log: function(message, exception) {
if (typeof console != 'undefined' && console.log)
console.log(message);
}
};
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Problem-using-Ajax-to-listen-to-a-queue-topic-tp3167287p3167522.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
this message in context:
http://activemq.2283324.n4.nabble.com/Problem-using-Ajax-to-listen-to-a-queue-topic-tp3167287p3167318.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
n some
destinations.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Problem-using-Ajax-to-listen-to-a-queue-topic-tp3167287p3167287.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
