Thanks for pointing that out, Alex. As I was not able to compile and run a
source version with the patch you mentioned applied, I´ll stay with this
"solution". My application is not in production yet.
I am looking forward to see your patch (hopefully) in the next release of
ActiveMQ.
Thank you
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 startup, like
> so:
>
> amq.removeListener(id, destination);
> amq.addListener(id, destination, callBack);
>
> N
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
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
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
On Sep 30, 2010, at 4:33 PM, jule wrote:
>
> 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?
Our plan (at my work) is to get
https://issues.apache.org/activemq/browse/AMQ-2948 accepted
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
On Sep 30, 2010, at 10:51 AM, jule wrote:
>
> 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.
If you rest
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
