If you register for consumer advisories, on your initial subscription, you will get the current state replayed to you.
The current state is also exposed via jmx. so you can code against the mbeans to find existing consumers. Then use advisories or poll jmx to see changes. http://activemq.apache.org/jmx.html On 21 May 2010 14:25, Markus Schaber <m...@soloplan.de> wrote: > > Hi, > > > Gary Tully wrote: > > > > lots of the information in the advisories is stored in properties and > > these > > properties are not automatically mapped into the stomp message so most of > > the information in the advisory is lost when it is consumed via stomp. > > It may be an easy enough fix if you are interested to have a go at a > > resolution. > > > > Ah, now I understand. Well, the more important thing is that the clients I > want to supervise are fixed to use STOMP. But it is possible for me to use > NMS/OpenWire or Java-Code in the supervising application. > > But as far as I can tell, the Advisory Messages only report changes. So how > can my supervisor application synchronize the current state when it starts > up? And how can that state be preserved during restarts of ActiveMQ or the > supervisor application? > > Pointers to documentation are welcome! > > Thanks! > -- > View this message in context: > http://old.nabble.com/Finding-out-when-client-is-offlin-tp28594744p28633797.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > > -- http://blog.garytully.com Open Source Integration http://fusesource.com
