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-topic-t
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
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;
