This sounds a bit odd; I'm not sure why its behaving like that. The maxInactivityDuration should be detecting inactivity on a connection and closing it.
http://incubator.apache.org/activemq/configuring-wire-formats.html I wonder if setting it to a small value helps? On 1/16/07, masterov <[EMAIL PROTECTED]> wrote:
Hey James, James.Strachan wrote: > > Just out of interest; are you sure the broker detected the loss of the > client? Depending on your OS and the settings, it might be its taking > the broker a while to detect client loss. e.g. 30 seconds from > pressing CTRL-C. > > So I wonder, if you look in JConsole, is the client connection gone > but you didn't receive an advisory? > That indeed is the problem: "the broker does not detect a client loss", and it's not a matter of 30 seconds, the number of consumers stays the same until the next message is sent to that topic, and only after that I get "RemoveInfo" and the number of consumers is decremented. Thanks to your response I realized that this is happening. So perhaps that is ok, and I should really work with this behaviour. For example if there was no message on a topic for a certain period of time - fire an empty message just to ensure that all "RemoveInfo" notifications are sent. Or is there an easier way? -- View this message in context: http://www.nabble.com/Detecting-lost-clients-tf2208237.html#a8393093 Sent from the ActiveMQ - User mailing list archive at Nabble.com.
-- James ------- http://radio.weblogs.com/0112098/
