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.
