Re: Finding out when client is offlin

great. thanks. will have a peek at it in the next few days. On 25 May 2010 14:43, James Casey wrote: > Hi Gary, > > I've worked up a fix for Advisories via STOMP - the patch is attached > to . > > It's a good start, but could probably do with a

Re: Finding out when client is offlin

Hi Gary, I've worked up a fix for Advisories via STOMP - the patch is attached to . It's a good start, but could probably do with a bit more work to clean up the message formats - it uses XStream to serialize the DataStructure object (and all th

Re: Finding out when client is offlin

Hi, Gary, Gary Tully wrote: > > 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 j

Re: Finding out when client is offlin

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.or

Re: Finding out when client is offlin

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

Re: Finding out when client is offlin

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 resolutio

Re: Finding out when client is offlin

Hi, Dejan, Dejan Bosanac wrote: > > the most natural way would be to use advisory messages ( > http://activemq.apache.org/advisory-message.html), but this is not yet > supported from Stomp (https://issues.apache.org/activemq/browse/AMQ-2098), > so you'd need to use Java to process this kind of

Re: Finding out when client is offlin

Hi Markus, the most natural way would be to use advisory messages ( http://activemq.apache.org/advisory-message.html), but this is not yet supported from Stomp (https://issues.apache.org/activemq/browse/AMQ-2098), so you'd need to use Java to process this kind of events. Cheers -- Dejan Bosanac -