Can you provide more detail regarding the problem. I assume you are using the amq.js file? If you are, the browser is constantly polling the server for data. If there is a connection problem, the browser is the first to know about it. In these cases, reconnect logic will have to exist in the browser.
-- jim jefetech wrote: > > Browsers occasionaly go dead and stop receiving JMS messages. What is the > best way to detect this and reconnect? > > I wrote a function that sends out a ping message through the jms every 3 > minutes, and if it's receives it sets a flag. I check that flag in 30 > seconds after the ping and if it's not set I prompt the user to reload > their browser. That seems hacky though and unreliable. Is there a bitter > way to detect the amq.addListener status and reconnect without refreshing > the browser? > > Thank you, > > Jeff > > > -- View this message in context: http://www.nabble.com/Detecting-lost-ajax-clients-tf3761822s2354.html#a12880356 Sent from the ActiveMQ - User mailing list archive at Nabble.com.