Hi Alex, unfortunately this is not supported at the moment as listeners are tied to the session. The right approach would be to use some clientId defined in your application, like we have for REST and pass it to the servlet. If you're interested in taking a stab at implementing this, I can point you to the code that should be improved.
Cheers -- Dejan Bosanac - http://twitter.com/dejanb Open Source Integration - http://fusesource.com/ ActiveMQ in Action - http://www.manning.com/snyder/ Blog - http://www.nighttale.net On Fri, Sep 10, 2010 at 6:46 PM, Alex Dean <a...@crackpot.org> wrote: > I have been testing a web page displaying activemq data via the AJAX > interface with AMQ 5.4. It works great when I have a single window open. > If I open the same page in a new browser window or tab, the new window/tab > updates correctly but the previously-open one stops updating. > > Firebug/Firefox in the previously-opened window starts reporting errors like > "No handler found to match message with id = display43066495". > 'display43066495' is the id used by the newly-opened window. I had tried > ensuring that both windows opened with unique ids, but this hasn't solved > the problem. > > I imagine this is due to the fact that both windows share the same session > id on the broker. Is there a way to work around this problem, so I can have > multiple windows open to the same amq/ajax-connected page? > > thanks, > alex >
