Which version of activemq are you using? There is a JIRA for connections not being removed ( https://issues.apache.org/jira/browse/AMQ-4100) otherwise, the appropriate way is to configure the timeout connection with "?websocket.maxIdleTimeout=<value>"
Can you try on the latest trunk and let us know if it's still an issue? On Mon, Oct 29, 2012 at 4:11 AM, blackhurstd <daniel.a.blackhu...@gmail.com>wrote: > > Hi, > > The number of topic consumers seems to increase every time I refresh the > stomp connection. I've tried closing down the browser yet the number of > consumers keeps increasing. > > I have a large number of subscribers connected to two active mq instances, > one master one failover (without using master slave config). Clients > connect > to both simultaneously. The master instance seems to be fine although the > slave keeps increasing until it runs out of file descriptors. I'm guessing > this is due to there been very few messages broadcasted. > > Is there any way to make activemq check the condition of the sockets? > > Thanks, > > Dan > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Idle-stomp-websockets-remain-connected-tp4658371.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > -- *Christian Posta* http://www.christianposta.com/blog twitter: @christianposta
