Thank you for your contributions.
Alex Dean-2 wrote:
>
>
> On Oct 8, 2010, at 5:09 AM, jule wrote:
>
>>
>> I found a (quite obvious) solution to this problem. I just added a call
>> to
>> removeListener() of amq.js just before adding my listener on startu
I found a (quite obvious) solution to this problem. I just added a call to
removeListener() of amq.js just before adding my listener on startup, like
so:
amq.removeListener(id, destination);
amq.addListener(id, destination, callBack);
Now it works perfectly fine for me. Maybe this should be incl
a test build with Maven,
applied the patch ("patch" reported one error, I considered it minor and
continued) and build again -> I tried to run the broker in the
assembly/src/release/bin directory but I got the following:
Jule$ assembly/src/release/bin/activemq start
INFO: Using defau
I am using "amq.js" and "amq_jquery_adapter.js" and when I run my application
with Chrome or Safari I get the error "Refused to set unsafe header
'Connection'".
I fixed this by borrowing the following lines from the latest release of
prototype.js and putting them into amq_jquery_adapter.js", star
Alex Dean-2 wrote:
>
>
>> For others facing the same problem: Meanwhile I found out that appending
>> a
>> "?ClientId=YourClientID" to the GET and POST urls (for either REST-API or
>> AJAX-API [uses REST-API]) will prevent this problem from showing up. I
>> guess
>> this will bypass the automat
Hi,
I see the following log message if a poll times out and an empty response is
received:
Error occurred in poll. HTTP result: 200, status: parsererror ->
amq_jquery_adapter.js:94
Investigating this with the JS debugging tools shows the brokers response:
xhr.responseText: " "
xhr.response
Hi Alex,
you´re right, reloading after restart will get it back to work. Thanks for
your explanation. Is there a schedule for the patch you mentioned?
For others facing the same problem: Meanwhile I found out that appending a
"?ClientId=YourClientID" to the GET and POST urls (for either REST-API
I just found out that this behaviour can also be reproduced with the
"chat"-example with an out-of-the-box configured ActiveMQ broker. If a
client browser is restarted, this example app breaks and the client cannot
receive anymore.
--
View this message in context:
http://activemq.2283324.n4.nabb
Hi there.
I have a problem (likely a lack of configuration) with ActiveMQ 5.4.1. I am
using ActiveMQ to allow a 1-to-1 conversation between two clients:
I have set up the Standalone Broker by extracting it, creating a new folder
in the "webapps"-folder, copied over META-INF and WEB-INF folders
